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
r2 fails to parse /proc/maps from the Android device via gdb remote protocol #21813
Comments
Can you try this branch? #21815 and see if my blindfix works? |
@trufae Wow, quick fix. I need to setup the dev env for this first. I have not tried to build yet. I simply installed with |
I managed to build with |
@trufae I tested this via
There's no way for me to reopen this ticket. Should I open a new one? |
I have reopen permissions 😎 |
Untested pr. need to find some time to test with real device #21858 can you give it a try? its not merged yet |
got the device setup and testing now |
Fixed and tested :) |
Thank you, @trufae! I will install from git soon and try. A local build doesn't work for me, only via |
Theres room for improvement but ill do that for the next release as its not a blocker. This should be good now :) thanks for reporting |
Environment
Description
When I connect to a
gdbserver
running on an Android Arm64 phone I get the following:It seems to fails to parse the /proc/maps for the target process. I checked the r2 code and seems to expect something more of a filename in last place. Would it be possible to ignore the regions that don't parse or fix up their name to be able to proceed with the debugging? At this point the parsing function aborts the debugger.
Test
I run the gdbserver on the phone like this:
gdbserver :1234 --attach $(pidof my.app.package.id)
I forward the the port to the host with
adb
:And I simply launch
r2
and run the following command there and the following output:No debugging is possible after this.
The text was updated successfully, but these errors were encountered: