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 gaudy, pyflamGaudily 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 colors!, gaudy, pyflam, ShinyLike 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 colors!, ShinyPython 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 trace