The disassembly in gdb is not ideal. The binding with source code lines is weird (even crash, which does use gdb beneath, does that better), I don't see the jump targets; furthermore, there's a lot more informations hidden in the DWARF2 which may be of some interest - like which code is inlined, or which register/stack address should contain some variable.

My goal is to search for a way how to improve that.

Looking for mad skills in:

gdb

This project is part of:

Hack Week 12

Activity Show All

  • almost 2 years ago: mkubecek liked gdb - better disassembly
  • almost 2 years ago: alnovak added keyword "gdb" to gdb - better disassembly
  • almost 2 years ago: alnovak started gdb - better disassembly
  • almost 2 years ago: alnovak originated gdb - better disassembly
  • Comments