For issues like https://bugzilla.redhat.com/show_bug.cgi?id=2381542#c3, GDB, spawned from CoreDumpCtl, recommends the DebugInfo package due to DebugInfoD not being able to provide the necessary libraries. However, per https://discussion.fedoraproject.org/t/where-is-chromiums-debuginfo-package/159053/2, these are not being produced. Reproducible: Always Steps to Reproduce: Encounter https://bugzilla.redhat.com/show_bug.cgi?id=2381542#c3. Actual Results: > ~~~ > Program terminated with signal SIGILL, Illegal instruction. > #0 0x000055fdf457c2e8 in ?? () > [Current thread is 1 (Thread 0x7fbecb9fc6c0 (LWP 5))] > Missing rpms, try: dnf --enablerepo='*debug*' install chromium-debuginfo-138.0.7204.100-1.fc42.x86_64 > ~~~ ...then: > ~~~ > Repositories loaded. > Failed to resolve the transaction: > No match for argument: chromium-debuginfo-138.0.7204.100-1.fc42.x86_64 > ~~~ ...then: > ~~~ > #0 0x000055fdf457c2e8 in ?? () > No symbol table info available. > ~~~ Expected Results: I should have symbols!
Also seeking this.
Might be worth noting that this isn't a limitation of chromium itself. I downloaded the latest chromium from https://www.chromium.org/getting-involved/download-chromium/ and then reproduced the crash and I can get a good stack trace in coredumpctl debug: (gdb) bt #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x00007fd5864981e3 in __pthread_kill_internal (threadid=<optimized out>, signo=6) at pthread_kill.c:89 #2 0x00007fd58643eafe in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x00007fd5864266d0 in __GI_abort () at abort.c:73 #4 0x0000564f08d82b45 in base::debug::BreakDebuggerAsyncSafe() () #5 0x0000564f08cdb1e3 in base::RepeatingCallback<void (char const*, int, std::__Cr::basic_string_view<char, std::__Cr::char_traits<char> >, std::__Cr::basic_string_view<char, std::__Cr::char_traits<char> >)>::Run(char const*, int, std::__Cr::basic_string_view<char, std::__Cr::char_traits<char> >, std::__Cr::basic_string_view<char, std::__Cr::char_traits<char> >) const & () #6 0x0000564f08cdb0a5 in logging::LogMessage::HandleFatal(unsigned long, std::__Cr::basic_string<char, std::__Cr::char_traits<char>, std::__Cr::allocator<char> > const&) const () #7 0x0000564f08cdad14 in logging::LogMessage::Flush() () #8 0x0000564f08cda67c in logging::LogMessage::~LogMessage() () #9 0x0000564f08cc8062 in logging::(anonymous namespace)::CheckLogMessage::~CheckLogMessage() () #10 0x0000564f08cc7d4b in logging::NotReachedNoreturnError::~NotReachedNoreturnError() () #11 0x0000564f0e92c520 in crash_reporter::internal::PlatformCrashpadInitialization(bool, bool, bool, std::__Cr::basic_string<char, std::__Cr::char_traits<char>, std::__Cr::allocator<char> > const&, base::FilePath const&, std::__Cr::vector<std::__Cr::basic_string<char, std::__Cr::char_traits<char>, std::__Cr::allocator<char> >, std::__Cr::allocator<std::__Cr::basic_string<char, std::__Cr::char_traits<char>, std::__Cr::allocator<char> > > > const&, base::FilePath*) () #12 0x0000564f0e922e08 in crash_reporter::InitializeCrashpad(bool, std::__Cr::basic_string<char, std::__Cr::char_traits<char>, std::__Cr::allocator<char> > const&) () #13 0x0000564f038522a6 in ChromeMainDelegate::PreSandboxStartup() () #14 0x0000564f07f011b2 in content::ContentMainRunnerImpl::Initialize(content::ContentMainParams) () #15 0x0000564f07eff3f5 in content::RunContentProcess(content::ContentMainParams, content::ContentMainRunner*) () #16 0x0000564f07eff707 in content::ContentMain(content::ContentMainParams) () #17 0x0000564f03850382 in ChromeMain () #18 0x00007fd5864285f5 in __libc_start_call_main (main=main@entry=0x564f038500f0 <main>, argc=argc@entry=42, argv=argv@entry=0x7ffc787690e8) at ../sysdeps/nptl/libc_start_call_main.h:58 #19 0x00007fd5864286a8 in __libc_start_main_impl (main=0x564f038500f0 <main>, argc=42, argv=0x7ffc787690e8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffc787690d8) at ../csu/libc-start.c:360 #20 0x0000564f0385002a in _start () (My issue turned out to be that newer versions of chromium require creating $HOME/.config/google-chrome/Crashpad (my solution), or setting XDG_CONFIG_HOME/XDG_CACHE_HOME, or setting --database on chrome_crashpad_handler somehow.)
Did GDB prompt you to download a package? If not, I'll presume that your crash merely didn't require the symbols that ours did. Otherwise, do you mean that the official binary has the symbols embedded?
> Did GDB prompt you to download a package? If not, I'll presume that your crash merely didn't require the symbols that ours did. Otherwise, do you mean that the official binary has the symbols embedded? I cleared cache with `rm -rf ~/.cache/debuginfod_client` and re-loaded the dump from the downloaded chromium and searched for chromium in the debuginfod output and it was not there and this was the only match: (No debugging symbols found in /opt/chromium/1491171/chrome-linux/chrome) I'm not changing the list of debuginfo servers so the stack symbolification must be due to embedded symbols. It's interesting that the top stack frame is in the system glibc: Downloading 4.48 K source file /usr/src/debug/glibc-2.41-8.fc42.x86_64/nptl/pthread_kill.c #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 44 return INTERNAL_SYSCALL_ERROR_P (ret) ? INTERNAL_SYSCALL_ERRNO (ret) : 0; (gdb) bt #0 __pthread_kill_implementation (threadid=<optimized out>, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 So even if Fedora's chromium is fully stripped, I wonder why gdb can't evaluate the top stack frame with Fedora's chromium which is presumably also in pthread_kill: Program terminated with signal SIGTRAP, Trace/breakpoint trap. #0 0x00005632074161f7 in ?? () Missing rpms, try: dnf --enablerepo='*debug*' install chromium-debuginfo-138.0.7204.157-1.fc42.x86_64 ffmpeg-libs-debuginfo-7.1.1-6.fc42.x86_64 vvenc-libs-debuginfo-1.13.1-3.fc42.x86_64 x264-libs-debuginfo-0.164-16.20231001git31e19f92.fc42.x86_64 x265-libs-debuginfo-4.1-2.fc42.x86_64 (gdb) bt #0 0x00005632074161f7 in ??? () #1 0x0000000000000000 in ??? () (gdb)
The top frame is in chromium-browser, so maybe the Fedora chromium crash is different somehow: Start Addr End Addr Size Offset File 0x00005631fb91f000 0x00005631fca0f000 0x10f0000 0x0 /usr/lib64/chromium-browser/chromium-browser 0x00005631fca10000 0x000056320864d000 0xbc3d000 0x10f0000 /usr/lib64/chromium-browser/chromium-browser 0x000056320864d000 0x0000563208f56000 0x909000 0xcd2c000 /usr/lib64/chromium-browser/chromium-browser
(In reply to kevin from comment #5) Considering that I once filed https://issues.chromium.org/issues/421207622#comment6, which is similar to https://bugzilla.redhat.com/show_bug.cgi?id=2381730#c0, the crashes differing would make more sense, because, otherwise, it would mean that each damn release channel of Chromium, whether Fedora's build, the official Chromium builds, or the official Chrome builds, all have different symbol inclusion policies in their CI. Have you tried the official Chrome RPM?
(In reply to Mr. Beedell, Roke Julian Lockhart (RJLB) from comment #6) Makes sense. At this point, it's hard for me to reproduce, but the one I downloaded with good symbolification is coming from https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Linux_x64/ using the script (linked to by Google on their https://www.chromium.org/getting-involved/download-chromium/ page) from https://raw.githubusercontent.com/scheib/chromium-latest-linux/refs/heads/master/update.sh It's interesting that it appears Fedora is completely stripping the binary: /usr/lib64/chromium-browser/chromium-browser: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 3.2.0, BuildID[sha1]=a8ce14c29d919ce9ac4478106dc002b7d04bbfbe, stripped I understand not having detailed debuginfo symbols (the purpose of this bug), but why completely strip the binary even of public exports?
This prevents me also reporting https://retrace.fedoraproject.org/faf/reports/1280635/ for https://bugzilla.redhat.com/show_bug.cgi?id=2361453#c18.
The same for https://retrace.fedoraproject.org/faf/reports/1278953/.
FEDORA-2025-2d4d91b00a (chromium-141.0.7390.54-1.fc41) has been submitted as an update to Fedora 41. https://bodhi.fedoraproject.org/updates/FEDORA-2025-2d4d91b00a
FEDORA-EPEL-2025-bff0433d38 (chromium-141.0.7390.54-1.el9) has been submitted as an update to Fedora EPEL 9. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-bff0433d38
FEDORA-EPEL-2025-96049efbd2 (chromium-141.0.7390.54-1.el10_2) has been submitted as an update to Fedora EPEL 10.2. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-96049efbd2
FEDORA-2025-37da05914f has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-37da05914f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-37da05914f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-bff0433d38 has been pushed to the Fedora EPEL 9 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-bff0433d38 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2025-96049efbd2 has been pushed to the Fedora EPEL 10.2 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-96049efbd2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-acc92fcc12 has been pushed to the Fedora 42 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-acc92fcc12` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-acc92fcc12 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-2d4d91b00a has been pushed to the Fedora 41 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-2d4d91b00a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-2d4d91b00a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2025-37da05914f (chromium-141.0.7390.54-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-96049efbd2 (chromium-141.0.7390.54-1.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-acc92fcc12 (chromium-141.0.7390.54-1.fc42) has been pushed to the Fedora 42 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2025-bff0433d38 (chromium-141.0.7390.54-1.el9) has been pushed to the Fedora EPEL 9 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2025-2d4d91b00a (chromium-141.0.7390.54-1.fc41) has been pushed to the Fedora 41 stable repository. If problem still persists, please make note of it in this bug report.