conditions: bug in condition assignments like foo = !!bar
commitcc488cf1761d0eefe14d8017368fe3bdbe074d57
authorDan Carpenter <dan.carpenter@oracle.com>
Wed, 23 Mar 2016 13:06:38 +0000 (23 16:06 +0300)
committerDan Carpenter <dan.carpenter@oracle.com>
Wed, 23 Mar 2016 13:06:38 +0000 (23 16:06 +0300)
tree1af6c0446695b6454157b418979f0146d7fec364
parent8ce971007bc3b5c5743093f4fa8679a827c84431
conditions: bug in condition assignments like foo = !!bar

The problem here is that say we have unmatched states, then we should
first try to see if we have the state in the cur stree instead of using
the default state.

I also moved a debug statement down some lines.

Reported-by: conchur@web.de
Signed-off-by: Dan Carpenter <dan.carpenter@oracle.com>
smatch_conditions.c