On 2020/11/06 17:56, Gabriele Svelto wrote:
[cross-posting to dev-platform]
Hello all,
I'm glad to announce that we switched our symbol scrapers for Linux
distributions to our new and improved Rust-based tooling [1]. This means
that when looking at crash reports or profiling you will not find stack
traces with missing or omitted function names anymore.
If you're tracking Linux crashes this might cause signature changes
starting with release version 83; the new signatures should be
significantly improved.
The impact of this change will be more visible to users on Fedora and
OpenSUSE.
Gabriele
[1] https://github.com/mozilla/dump_syms/
_______________________________________________
Does this support split dwarf object files?
I use GCC -split-dwarf to generate separate object and dwarf files
locally to speed up gdb startup.
Unfortunately, this is not grokked by stack dump code since rust-based
one replaced the older ruby code that used objdump, etc.
So I get either empty or undecoded stack dump there.
I have not the time to work around on this issue, even the hack to
revert back to the old code if the object files turn out to be
split-dwarf type.
Just wondering.
(Maybe I should switch back and not to use -split-dwarf until I need to
run gdb seriously. There WERE times that I needed to run thunderbird
under gdb to check subtle bugs.)
Thank you for improving the backends.
Chiaki
_______________________________________________
dev-platform mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-platform