News for hackers. Stuff that matters.
Re:Improving Firefox stability on Linux by nyanpasu64 on Wednesday May 19, 2021 @06:26PM (#27215336)
How do you extract symbols from official binary builds of Arch? According to official documentation (https://wiki.archlinux.org/title/Debug_-_Getting_Traces and bug report threads I've seen), Arch lacks both debug packages and symbols bundled with binary packages. As a result, if you want to debug an app crash on Arch, you need to quit the program, recompile the app from source with your makepkg.conf set to !strip, then try to reproduce the bug in your new build.

It seems Firefox has a script at https://github.com/gabrielesvelto/symbol-scrapers/blob/maste..., but I haven't investigated what it does. In any case, this information should be integrated into the Arch Wiki.

Re:Improving Firefox stability on Linux by gsvelto on Thursday May 20, 2021 @12:58AM (#27217548)
Only public symbols and unwinding information is extracted from Arch packages because they don't have debuginfo like other distros. It's better than nothing.
Re:Improving Firefox stability on Linux by nyanpasu64 on Thursday May 20, 2021 @10:44AM (#27221754)
Well that's unfortunate to hear :( Hoping Arch can fix releasing debug symbols for official binary builds soon... but I don't expect it to happen soon.

Also how does unwinding info help during debugging? Does gdb use it? Do I need special reverse-engineering tools to extract useful information?

Re:Improving Firefox stability on Linux by gsvelto on Saturday May 22, 2021 @04:05AM (#27244533)
Arch already uploads symbols for their Firefox builds so that's OK, it's the dependencies that are missing. Unwinding information is used to produce accurate stacks. If it's lacking our unwinder has to rely on heuristics to discover the frames on the stack and those might end up producing suboptimal traces.