Skip to content

{ Tag Archives } gdb

unified JS/C++ backtraces, colorized backtraces, colorized source listing for gdb 7.3/archer-trunk updated

gdb has had integrated python support for some time and it is truly awesome.  The innards have changed here and there, so my previous efforts to show colorized/fancy backtraces, show colorized source listings, and provide unified JS/C++ mozilla backtraces (with colors still) have experienced some bit-rot over time. I have de-bitrotted the changes, hard.  Hard […]

Also tagged , ,
2011 03 30 Andrew Sutherland Debugging Comments (3)

prototype unified JavaScript/C++ back-traces for Mozilla in (archer) gdb

As far as I know (and ignoring my previous efforts on chroniquery along these lines), up until now you had your C/C++ Mozilla backtraces via gdb (chocolate) and your JS backtraces via “call DumpJSStack()” or the debugger keyword from within JS (peanut butter), but these two great flavors had never come together to make a […]

Also tagged ,
2009 09 12 Andrew Sutherland Debugging
Mozilla Comments (2)

gaudily syntax-highlighted code listings in (archer) gdb

Gaudily syntax-highlighted code listing in gdb joins the gaudy gdb plugin family!  (Other members include gaudily colorized backtraces, which you can also see in the bottom of the screenshot.)  This, of course, requires gdb with python crammed inside.  It might require one crammed a few months ago too; I haven’t updated my archer-gdb repo for […]

Also tagged , , ,
2009 04 25 Andrew Sutherland Debugging Comments (1)

gaudily colorized gdb backtraces! woo!

Like many people who have overdosed on syntax highlighting and other forms of colorization, my brain is no longer able to process monochrome text displays.  Which is why I have been so excited about gdb with python crammed inside.  (The good sense of “crammed”, wherein one is cramming cookies in one’s mouth.)  I have perverted […]

Also tagged ,
2009 03 04 Andrew Sutherland Debugging
Visualizing Comments (5)

the beginnings of a gdb execution trace visualization

Python code driving gdb via the mi2 interface (using pexpect and pyparsing) begets a trace file. Python code processing the trace file begets an html document (with syntax highlighting thanks to pygments.) The above is just a screenshot of the output, which you can actually browse here. The “visualization” is pretty simple. Lines of code […]

Also tagged
2007 04 25 Andrew Sutherland Debugging
Program Execution
Visualizing Comments Off on the beginnings of a gdb execution trace visualization