Pwndbg: gdbpwn feature parity

Created on 1 May 2017 · 6Comments · Source: pwndbg/pwndbg

[ ] libc : Print the base address of libc
[ ] ld : Print the base address of ld
[ ] codebase : Print the base of code segment
[ ] heap : Print the base of heap
[x] got : Print the Global Offset Table infomation
[ ] dyn : Print the Dynamic section infomation
[ ] findcall : Find some function call
[ ] bcall : Set the breakpoint at some function call
[ ] tls : Print the thread local storage address
[ ] at : Attach by process name
[ ] findsyscall : Find the syscall
[ ] fmtarg : Calculate the index of format string
- You need to stop on printf which has vulnerability.
[ ] force : Calculate the nb in the house of force.
[ ] heapinfo : Print some infomation of heap
[ ] chunkinfo: Print the infomation of chunk (Address of victim)
[ ] chunkptr : Print the infomation of chunk (Address of user ptr)
[ ] mergeinfo : Print the infomation of merge (Address of victim)
[ ] printfastbin : Print some infomation of fastbin
[ ] tracemalloc on : Trace the malloc and free and detect some error .
- You need to run the process first than tracemalloc on, it will record all of the malloc and free.
- You can set the DEBUG in pwngdb.py , than it will print all of the malloc and free infomation such as the screeshot.
[ ] parseheap : Parse heap layout

feature help wanted

Source

zachriggle

👍4

All 6 comments

Just leaving link here: https://github.com/scwuaptx/Pwngdb

disconnect3d on 2 May 2017

I have refactored some features in Pwngdb with pwndbg feature, but I have some questions:

Will you keep the module name as pwndbg or rename to gdbpwn(as title of this issue)?
The heap feature will conflict with the original heap command. Maybe we can rename all features about printing base to regular names.

0xddaa on 9 May 2017

There's no need for them to be in a named sub module like that. Just
integrate them as normal commands ❤️
On Tue, May 9, 2017 at 10:27 AM 0xddaa notifications@github.com wrote:

I have refactored some features
https://github.com/0xddaa/Pwngdb/tree/master/pwndbg in Pwngdb with
pwndbg feature, but I have some questions:

Will you keep the module name as pwndbg or rename to gdbpwn(as
title of this issue)?

The heap feature will conflict with the original heap command.
Maybe we can rename all features about printing base to regular names.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pwndbg/pwndbg/issues/259#issuecomment-300200897, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAG0GE4quZ4YktX3ksXdrl-LRSUu5u82ks5r4IXFgaJpZM4NNV6I
.