question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Pwndbg no longer shows addresses of operations

See original GitHub issue

I recall in the past, Pwndbg would calculate the address of an operation, e.g.

 ► 0x8048409 <main+30>     mov    eax, dword ptr [ebp - 8]

Would show the address of [ebp - 8] and its chained contents. This is no longer the case.

Is this disabled behind a flag, broken, or was it removed at some point? Super useful functionality. It existed before the current emulator, so perhaps it’s gone now?

Edit: It looks like pwndbg/disasm/arch.py still has all of the plumbing but we stopped showing it?
Edit 2: Did I just never finish the functionality? 😦

Issue Analytics

  • State:open
  • Created 3 years ago
  • Comments:9 (9 by maintainers)

github_iconTop GitHub Comments

1reaction
Arusekkcommented, Jul 25, 2020

After #801 a test fails, because of showing the symbol twice (not really helpful when one wants to see jump addresses): https://travis-ci.org/github/pwndbg/pwndbg/builds/710915914#L931-L934

1reaction
zachrigglecommented, Jul 1, 2020

I’d avoid telescope for disassembly unless we can limit it to real symbols

On Tue, Jun 30, 2020 at 7:10 PM Disconnect3d notifications@github.com wrote:

Also:

Would show the address of [ebp - 8] and its chained contents.

I think we never telescoped this and only showed a dereferenced value. Maybe we should just show a telescope with a depth of 1 here?

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

Zach Riggle

Read more comments on GitHub >

github_iconTop Results From Across the Web

[Bug] pwndbg shows incorrect stack context · Issue #460
In some binaries, pwndbg will show the incorrect stack context, for example (sorry for not providing the testing binary, it requires a lot ......
Read more >
GDB and PWNDBG Cheat Sheet (DRAFT) by cactuarnation
A cheatsheet for debugging 64-bit binaries with GDB and PWNDBG. This is a draft cheat sheet. It is a work in progress and...
Read more >
gdb can't access memory address error
When I type x/xw 0x208c it gives me back error which says Cannot access memory at address 0x208c. The disassembly for your program...
Read more >
binary analysis - Dumping the GOT with gdb at run time
There are a couple of options for this. Use pwndbg or gef. They have a command called got which looks like this. gef➤...
Read more >
Debugging with gdb - Examining the Symbol Table
Open-source document that explains how to use GDB to debug programs. ... operations (such as assignments or function calls) inside it do not...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found