Open op2786 opened 1 year ago
This has been discussed and is absolutely on the plan for the current stable release. I think there's another issue tracking it but in the meantime I'll take this and if we find the other issue it's a duplicate of we'll clear it up later.
If we reverse engineered a PE that have stack cookie protection, some functions have a code fragment that belongs to stack cookie protection like this in the beginning of the function:
And of course there is another code fragment that calls to __security_check_cookie function at the bottom of the function.
I guess that code fragments making decompiler output a little bit dirty. Most of the time we don't care about that code fragment. It would be nice to have an option to hide them.