SIGILL coredump and Linux builds debug symbols
Hello everyone,
Is there any plan to not stripping debug symbols (or offering them in a package) for Beta/Dev builds of Edge on Linux or offering them as a package?
And if not, why? I get stripping them for space efficiency, but usually there’d be a microsoft-edge-beta-debugsym/devel package with it for such cases.
This is prompted by getting a SIGILL tab worker crash every now and then (Edge Beta channel on Fedora), and would like to investigate, but I’m unable to do much with the backtrace I get back since it is all mangled.
It’s not super frequent, but I got ~100 of these over the past year, and it would be helpful for us (and for Microsoft in turn) if we could help look into what is happening.
I suspect the issue lies with hardware-accelerated DOM rendering (since nearly all Linux browser issues seem to originate in the sad history of Nvidia GPUs on it), but I’d like some conclusive proof or to be able to get the bug looked into at some point.
Thanks
Hello everyone, Is there any plan to not stripping debug symbols (or offering them in a package) for Beta/Dev builds of Edge on Linux or offering them as a package?And if not, why? I get stripping them for space efficiency, but usually there’d be a microsoft-edge-beta-debugsym/devel package with it for such cases. This is prompted by getting a SIGILL tab worker crash every now and then (Edge Beta channel on Fedora), and would like to investigate, but I’m unable to do much with the backtrace I get back since it is all mangled. It’s not super frequent, but I got ~100 of these over the past year, and it would be helpful for us (and for Microsoft in turn) if we could help look into what is happening. I suspect the issue lies with hardware-accelerated DOM rendering (since nearly all Linux browser issues seem to originate in the sad history of Nvidia GPUs on it), but I’d like some conclusive proof or to be able to get the bug looked into at some point. Thanks Read More