| commit | dc78cc525bdb7332410c1d2642103d9bdc5bd7a2 | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Tue, 13 Dec 2016 10:53:51 +0000 (13 13:53 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Tue, 13 Dec 2016 10:53:51 +0000 (13 13:53 +0300) | ||
| tree | 6abd4970dab11c9bd82a03524bc377aa48465539 | treesnapshot (tar.gz zip) |
| parent | 8dd4e9766d05d67f2174c5566e5313368c866b5f | commitdiff |
function_hooks, db: use INTERNAL as the marker for a new function return
The problem here is that you can have cases where two functions have the
same return_id so a new function is not detected. Say you have a function
hook so really it's just the same function called from two places and it
has only one return. In that scenario, it's very easy for this to happen.
Using INTERNAL should work and that should always be the first row of any
return_info.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
The problem here is that you can have cases where two functions have the
same return_id so a new function is not detected. Say you have a function
hook so really it's just the same function called from two places and it
has only one return. In that scenario, it's very easy for this to happen.
Using INTERNAL should work and that should always be the first row of any
return_info.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
| smatch_function_hooks.c | diffblobblamehistory |