| commit | 75759d5ee20e9b4db0bc392bd4c659af31e3b8f8 | |
| author | Dan Carpenter <dan.carpenter@oracle.com> | |
| Thu, 20 Sep 2018 11:44:54 +0000 (20 14:44 +0300) | ||
| committer | Dan Carpenter <dan.carpenter@oracle.com> | |
| Thu, 20 Sep 2018 11:44:54 +0000 (20 14:44 +0300) | ||
| tree | 640eb875d979267ebad397ddd8f6d817bc92bdd9 | treesnapshot (tar.gz zip) |
| parent | 74e4bc2f267ff1348a5b3bc78831b7ceb1256691 | commitdiff |
param_set: handle when the stack variable was modified better
Say you have a function like strcmp() which takes a parameter s1 does
"s1++;". We need to save that "s1" was modified, because we want
param_was_set() to work. We don't want to save that *s1 was set, because
it actually wasn't. And then generally if the stack variable changes, we
don't want to put that *s1 type stuff was changed (because it wasn't) so
we need to insert "s1" into the &set_list.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
Say you have a function like strcmp() which takes a parameter s1 does
"s1++;". We need to save that "s1" was modified, because we want
param_was_set() to work. We don't want to save that *s1 was set, because
it actually wasn't. And then generally if the stack variable changes, we
don't want to put that *s1 type stuff was changed (because it wasn't) so
we need to insert "s1" into the &set_list.
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
| smatch_param_set.c | diffblobblamehistory |