Hi,
I am writing here in relation to:
https://bugs.llvm.org/show_bug.cgi?id=39720
because of earlier advice given in regards to it:
Maybe post that binary and a corresponding core dump somewhere, so
somebody else can load those in a debugger? Or let your favorite crash
reporting tool (catchsegv or any of the Linux built-in crash reporters)
generate a full report, and post it in the PR?
In any case, you could try the following. Make sure the gdb package is
installed, then run:
gdb /opt/ungoogled-chromium/chrome
When gdb is finished loading the executable, type "run", and wait until
the program crashes. Then execute the following gdb commands:
bt full
info registers
disassemble
and post the full output of those commands in the PR.
-Dimitry
Maybe post that binary and a corresponding core dump
somewhere, so somebody else can load those in a
debugger?
# du -hs /opt/ungoogled-chromium/
288M /opt/ungoogled-chromium/
# du -hs /opt/ungoogled-chromium/chrome
199M /opt/ungoogled-chromium/chrome
I don't know where to post something of such size. But
using the shared build scripts it can be reproduced
quite easily.
Or let your favorite crash reporting tool (catchsegv
or any of the Linux built-in crash reporters)
generate a full report, and post it in the PR?
I have no idea what you are talking about (not a
developer as mentioned). I checked but couldn't find
such tool:
# zypper se catchsegv
Loading repository data...
Reading installed packages...
No matching items found.
In any case, you could try the following. Make sure
the gdb package is installed, then run:gdb /opt/ungoogled-chromium/chrome
When gdb is finished loading the executable, type
"run", and wait until the program crashes. Then
execute the following gdb commands:bt full
info registers
disassembleand post the full output of those commands in the PR.
Done: