-
Notifications
You must be signed in to change notification settings - Fork 26
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
GDB "find" crashes emulator #2
Comments
Hi, |
By "emulator console" I mean the output of No matter what Example:
My AVD
From your slides/demos, I saw that your emulator has 4 GB of memory. I thought maybe that causes the issue, but changing to Thank you for your help! |
Hi, Unfortunately, we were not able to reproduce your bug. According to the info you have given, it seems like it is not a bug related to emuroot. We hope you will find another gdb/machine configuration that will work for you. |
I get the same error. I think it is due to this change added in I solved it using: |
Black'ifyed it a bit and fixed issue airbus-seclab#2
Hi I am the pygdbmi maintainer. I just released v0.10.0.1 with cs01/pygdbmi#56. Hopefully it fixes the issue you were hitting. Sorry for the inconvenience. |
Hi, and thank you for the tool, looks really promising.
I've encountered an issue that when I start the script, it crashes the emulator when the GDB "find" command executes.
In the emulator console, I get this error message:
Things I've tried:
1. Different versions:
I tried multiple Android versions (from the supported list) but no success.
2. Executing the find manually:
When manually connecting to the remote GDB, and executing the
find 0xc0000000, +0x40000000, "MAGICNAME"
, it crashes the same way.3. Changing the start of the search:
I tried changing
0xc0000000
to0x0
, and that run successfully, and did find one promising addreess which looks like atask_struct
(has 2 same pointers ataddr-8
andaddr-4
), but it points to acred
struct which is just full of0x00
, so its probably not the real one.Is there any way to fix this issue and get the script working?
Is this an issue with the emulator/local config?
Thanks,
David
The text was updated successfully, but these errors were encountered: