You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems like alloca_probe is messing with the stack size calculations, I also have another function where it did this, it specially happens on functions with large stacks. Do you have a clue how to fix it? I tried but couldnt figure it out. There is many stack strings in those functions, they seem to be constructed in part with XMM registers, though some smaller functions that did the same thing ironstrings was able to find strings without an issue. I tried other tools as well like flare-floss, stackstrings, nothing worked. ironstrings is what found the most strings in this sample, but still missing quite a few.
Hello!
I have a function at 0x1802b4d40 in this Windows PE x64 file
sample.txt (ignore extension its a dll, github wouldnt upload otherwise)
It seems like alloca_probe is messing with the stack size calculations, I also have another function where it did this, it specially happens on functions with large stacks. Do you have a clue how to fix it? I tried but couldnt figure it out. There is many stack strings in those functions, they seem to be constructed in part with XMM registers, though some smaller functions that did the same thing ironstrings was able to find strings without an issue. I tried other tools as well like flare-floss, stackstrings, nothing worked. ironstrings is what found the most strings in this sample, but still missing quite a few.
Here's the program output:
ironstrings2.log
Thanks a lot!
The text was updated successfully, but these errors were encountered: