Possible GEF dereference issue with gef-remote
#1080
Comments
|
Hi @hyjun0407 Try using the latest version of GEF from |
|
Hi guys, I'm facing this same problem on ubuntu, and I don't understand why. I used kali linux and it was possible to see the stack view, but for some reason in ubuntu it is not possible to do this. |
|
Marked as stale as this needs more info. |
hugsy
changed the title
dereference issue with gef-remote
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. You can reopen it by adding a comment to this issue. |
|
The same happens for me when I debug a local coredump. Maybe the issue happens when the program is not currently running locally? I can provide you with the coredump if needed. |
It seems the stack is not marked as mapped in `info proc mappings`.But it is in `maintenance info sections`. |
|
I'd guess it's caused by #1046. (In support of this, the bug appears with version 2024.06 but not in 2024.01.) |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. You can reopen it by adding a comment to this issue. |
|
. |
|
@heinrich5991 can you try reverting that one PR to confirm if it's that issue? If it's not the |
|
I bisected the issue between 2024.01 and 2024.06 to find that c9a8b18 is indeed the first commit with this bug. Easily reverting that commit wasn't possible on master: |
|
Reproduction: #include <stdlib.h>
int main() {
abort();
}@Grazfather Could the need-more-info label be removed if that's the one triggering the stale bot? |
|
OK yeah I can reproduce. That is annoying. Why would |
|
I had time to root cause this. AFAICT the issues reported by @heinrich5991 and @hyjun0407 are different. What @hyjun0407 reported is now being fixed in #1151 (not merged yet). It was coming from a bad support of qemu-user. This PR improves it and offers the possibility to use a mock layout if none was reported by qemu (for old versions). So this issue is now on the process of being fixed. @heinrich5991 issue is specific to coredumps, which do not store stack layout in This is not a perfect solution but it's worth commenting, because those 2 issues are different despite seemingly similar. |
4 tasks
|
Update: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
GEF+GDB version
Operating System
WSL No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.4 LTS Release: 22.04 Codename: jammy
Describe the issue you encountered
qemu-aarch64-static -g 1234 ./prob
When I run the command with and proceed to gef-remote localhost 1234 with gdb-multiarch, Stack View is not available as above.
when i enter 'tele', it said [!] Unmapped address: '$sp' .
Do you read the docs and look at previously closed issues/PRs for similar cases?
No
Architecture impacted
Describe your issue. Without a proper reproduction step-by-step, your issue will be ignored.
qemu-aarch64-static -g 1234 ./prob
When I run the command with and proceed to gef-remote localhost 1234 with gdb-multiarch, Stack View is not available as above.
when i enter 'tele', it said [!] Unmapped address: '$sp' .
Minimalist test case
Use this field for a minimal code to compile and spot the issue:
You can also provide a Dockerfile if you prefer
Additional context?
The text was updated successfully, but these errors were encountered: