(2013/01/08 13:13), ishikawa wrote: > On (2013年01月08日 13:03), Joshua Cranmer wrote: >> On 1/7/2013 10:00 PM, ishikawa wrote: >>> If we can coerce the built-in traceback function to print something more >>> meaningful, or >>> if someone can suggest a way to attach gdb to a run of TB during "make >>> mozmill" session so that I can get a meaningful backtrace [*IF* gdb >>> can work out meaningful backtrace under the circumstances], that would be >>> appreciated. >>> >> >> There is a script called mozilla-central/tools/fix-linux-stack.pl. Pipe the >> output of your stack trace through that script, and you will get a useful >> one. > > Thank you! will try. (Hmm, comm-central has it under > mozilla/tools/rb/ ) > > Report back tomorrow. > > TIA >
It took me a while to figure out that the script needs to be run under the same directory where the original executable is located and also the arguments to the script itself. SYNOPSIS fix-linux-stack.pl logfile It seems that the script (in comm-central) understands that the user is interested in TB binary and resolves the numerical values into symbolic names ( I wonder, why, it was not doable in the C code.) Anyway, it works and I post first such log with resolved stack trace to https://bugzilla.mozilla.org/show_bug.cgi?id=828587 (It is not directly related to the bug in question, but is nice to see the comprehensible stack when we look at the log. For other bugs, the symbolic dump should be very helpful.) Thank you again. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
