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 gdb, pyflamIf you develop for the mozilla platform, you might be used to error messages like the above. (Or you might wish you got error messages like the above…) An uncaught javascript exception has resulted in a message in the error console as well as some equivalent stdout spew because it’s a debug build. While any [...]
Also tagged colors!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 colors!, gdb, pyflam, Shiny