How have the GDB pretty-printers been working out, for those of you who debug JS C++ on Linux?
While the Mozilla source tree includes GDB pretty-printers for JavaScript types (see js/src/gdb/README) since December 2012, GDB does not automatically load them when debugging a program that uses libxul.so. So people debugging browser C++ don't get them unless they take magic steps to turn them on. That was a deliberate decision, made when the pretty-printers first landed: we were concerned that the pretty-printers were relatively young code, and that enabling them for pretty much every developer debugging Mozilla C++ code would mean that any problems would have a wide impact. But the pretty-printers have been enabled by default for the SpiderMonkey shell and test programs for a few months now. We've fixed a few problems, but I think, overall, they've been okay. They're working out okay for me, but the author often has a different experience of his code than others do; how has it been for you? Is it valuable enough to inflict on everyone else, or too flaky to be worthwhile? _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
