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
[Bug] vmmap command 'offset' column actually shows size #1096
Comments
mjklbhvg
pushed a commit
to mjklbhvg/gef
that referenced
this issue
May 1, 2024
mjklbhvg
pushed a commit
to mjklbhvg/gef
that referenced
this issue
May 1, 2024
Fix the Offset column in the `vmmap` command by getting the offset from the correct column in `parse_gdb_info_proc_maps`.
mjklbhvg
added a commit
to mjklbhvg/gef
that referenced
this issue
May 1, 2024
Fix the Offset column in the `vmmap` command by getting the offset from the correct column in `parse_gdb_info_proc_maps`.
hugsy
pushed a commit
that referenced
this issue
May 19, 2024
## Description Fix the Offset column in the `vmmap` command by getting the offset from the correct column in `parse_gdb_info_proc_maps`. Before: ``` gef➤ vmmap [ Legend: Code | Heap | Stack ] Start End Offset Perm Path 0x0000555555554000 0x0000555555558000 0x0000000000004000 r-- /usr/bin/ls 0x0000555555558000 0x000055555556e000 0x0000000000016000 r-x /usr/bin/ls 0x000055555556e000 0x0000555555577000 0x0000000000009000 r-- /usr/bin/ls 0x0000555555577000 0x0000555555579000 0x0000000000002000 r-- /usr/bin/ls 0x0000555555579000 0x000055555557a000 0x0000000000001000 rw- /usr/bin/ls 0x000055555557a000 0x000055555557b000 0x0000000000001000 rw- [heap] ``` After: ``` gef➤ vmmap [ Legend: Code | Heap | Stack ] Start End Offset Perm Path 0x0000555555554000 0x0000555555558000 0x0000000000000000 r-- /usr/bin/ls 0x0000555555558000 0x000055555556e000 0x0000000000004000 r-x /usr/bin/ls 0x000055555556e000 0x0000555555577000 0x000000000001a000 r-- /usr/bin/ls 0x0000555555577000 0x0000555555579000 0x0000000000023000 r-- /usr/bin/ls 0x0000555555579000 0x000055555557a000 0x0000000000025000 rw- /usr/bin/ls 0x000055555557a000 0x000055555557b000 0x0000000000000000 rw- [heap] ``` info proc mappings: ``` gef➤ info proc mappings process 18800 Mapped address spaces: Start Addr End Addr Size Offset Perms objfile 0x555555554000 0x555555558000 0x4000 0x0 r--p /usr/bin/ls 0x555555558000 0x55555556e000 0x16000 0x4000 r-xp /usr/bin/ls 0x55555556e000 0x555555577000 0x9000 0x1a000 r--p /usr/bin/ls 0x555555577000 0x555555579000 0x2000 0x23000 r--p /usr/bin/ls 0x555555579000 0x55555557a000 0x1000 0x25000 rw-p /usr/bin/ls 0x55555557a000 0x55555557b000 0x1000 0x0 rw-p [heap] ```
Fixed by 13d1de2 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
GEF+GDB version
Operating System
LSB Version: 1.0 Distributor ID: VoidLinux Description: Void Linux Release: rolling Codename: void
Describe the issue you encountered
As the title says, the column "offset" in the vmmap output appears to actually show section size.
I am pretty sure this happened in this commit:
c9a8b18
I can reproduce with this commit, but not the commit before.
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.
gdb /bin/ls
start
vmmap
info proc mappings
Minimalist test case
No response
Additional context?
The text was updated successfully, but these errors were encountered: