-
-
Notifications
You must be signed in to change notification settings - Fork 59
Returning a released pointer from RangeDetails::with_address #120
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Nice catch! The upstream code is (for linux) https://github.com/frida/frida-gum/blob/a50dae75a25cb7fe95ed09883527dbd6777f28be/gum/backend-linux/gumprocess-linux.c#L1398. I will attempt a fix now. |
@mkravchik can you try this fix and confirm it is working? |
Oh wait. I'm dumb... This doesn't fix at all... |
Ok. Try now |
I tried it, and it looks good. In the meantime (until the version is out) I've found the following workaround useful:
|
I'll wait till the next frida version to release. |
Hi,
I consistently encountered this in the code I'm debugging. There is a call to RangeDetails::with_address. The returned value is complete nonsense.
When I debug it, I can see that when the save_range_details_by_address is called, it is passed a pointer to a
details
struct with correct data. However when we get back to with_address, the pointer points to garbage. I can only assume that the native Gum has freed this object and don't see anything preventing it from doing so.The text was updated successfully, but these errors were encountered: