Kudos & clarification #1292
Unanswered
forensicmike
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
First in case some of the maintainers read this I want to say thank you for such an amazing repository, I've been using qiling framework for the last week and I am blown away by how cool it is and I know I am just scratching the surface.
One question I had. I am attempting to emulate x86 linux and I've found that it was necessary to essentially handle all malloc calls by my target binary because otherwise the app crashes when it hits an instruction that references gs:[0] which I understand isn't implemented and likely just returns 0.
I can only imagine this is something that comes up often but I haven't been able to find any docs about it specifically. In the meantime I have hooked every call to malloc and replaced it with my own implementation with a counter and a blank page mapped with
ql.mem.map
.Are there any other options that don't involve patching every call to malloc? Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions