| commit | da8711e943825347664b85666d08126c1ed3becc | |
| author | Dan Carpenter <error27@gmail.com> | |
| Thu, 6 Apr 2023 09:23:26 +0000 (6 12:23 +0300) | ||
| committer | Dan Carpenter <error27@gmail.com> | |
| Thu, 6 Apr 2023 09:23:26 +0000 (6 12:23 +0300) | ||
| tree | 6072e52f25ff741d7ba0eb520831b68f4c83708f | treesnapshot (tar.gz zip) |
| parent | 25c8199f66abdaa4d632040f54b01872a2ac43ce | commitdiff |
unwind: introduce &unknown state
I wrote this patch some time back and I forget what I was thinking about.
Looking at it now, I would have used the &released state instead of the
unknown state. But at the time, I guess I was like, "Let me create a
state to represent when I am lost." It's actually a more powerful than
&released because if something is ever &unknown then it counts as being
&released on every path.
Signed-off-by: Dan Carpenter <error27@gmail.com>
I wrote this patch some time back and I forget what I was thinking about.
Looking at it now, I would have used the &released state instead of the
unknown state. But at the time, I guess I was like, "Let me create a
state to represent when I am lost." It's actually a more powerful than
&released because if something is ever &unknown then it counts as being
&released on every path.
Signed-off-by: Dan Carpenter <error27@gmail.com>
| check_unwind.c | diffblobblamehistory |