Webkit2gtk4.1 crashes as started from Evolution: https://gitlab.gnome.org/tasali/webkit2gtk/-/issues/1 To get a backtrace out of the core files I have installed the webkit2-debuginfo packages (see install.msg), but these seem to be infunctional: $ gdb -core core-Storage.13195.localhost.1671385368 Missing separate debuginfo for the main executable file Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/94/766ab957e40b5061836e6e6532d8a5597f89f6 Core was generated by `/usr/libexec/webkit2gtk-4.1/WebKitNetworkProcess 7 28'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0xb0c16773 in ?? () [Current thread is 1 (LWP 13254)] I remember there was a problem with the separate debuginfo packages under Mageia (before 9) also for other packages. Gdb simply does not find the separate debuginfo.
Created attachment 13584 [details] debuginfo install console messages Here: urpmf does not find the hash requested by gdb: # urpmf 766ab957e40b5061836e6e6532d8a5597f89f6 http://mirrors.mageia.org/api/mageia.9.i586.list: media/core/release/media_info/20221218-021424-files.xml.lzma http://mirrors.mageia.org/api/mageia.9.i586.list: media/core/updates/media_info/20220402-205512-files.xml.lzma http://mirrors.mageia.org/api/mageia.9.i586.list: media/nonfree/release/media_info/20221217-234916-files.xml.lzma http://mirrors.mageia.org/api/mageia.9.i586.list: media/nonfree/updates/media_info/20220402-205356-files.xml.lzma #
Thank you for the report. Since the problem could be generic, assigning to BaseSystem. If it is actually package-specific, pass it back & I will re-assign for Webkit2.
Assignee: bugsquad => basesystem
confirmed for gdb-12.1-6.mga9.
confirmed for the newest updates of webkit2gtk: libwebkit2gtk4.0_37-2.38.3-1.mga9 libwebkit2gtk4.0_37-debuginfo-2.38.3-1.mga9 libwebkit2gtk4.1_0-2.38.3-1.mga9 libwebkit2gtk4.1_0-debuginfo-2.38.3-1.mga9 libwebkit2gtk5.0_0-2.38.3-1.mga9 libwebkit2gtk5.0_0-debuginfo-2.38.3-1.mga9 libwebkit2gtk-gir4.0-2.38.3-1.mga9 libwebkit2gtk-gir4.1-2.38.3-1.mga9 libwebkit2gtk-gir5.0-2.38.3-1.mga9 webkit2gtk4.0-2.38.3-1.mga9 webkit2gtk4.0-debuginfo-2.38.3-1.mga9 webkit2gtk4.1-2.38.3-1.mga9 webkit2gtk4.1-debuginfo-2.38.3-1.mga9 webkit2gtk5.0-2.38.3-1.mga9 webkit2gtk5.0-debuginfo-2.38.3-1.mga9
Exactly how did you confirm this? Did you generate a new core dump using the latest versions? Using urpmf, I was able to locate and install all the debug info requested by gdb for a similar core dump (see bug 31294).
CC: (none) => mageia
Yes, I have generated new core dumps with the packages from above: # gdb -core core-Storage.1937.localhost.1672334056 Missing separate debuginfo for the main executable file Try: yum --enablerepo='*debug*' install /usr/lib/debug/.build-id/b4/7ed1465d37193048c31cc317564637c5d1c938 Core was generated by `/usr/libexec/webkit2gtk-4.1/WebKitNetworkProcess 21 39'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0xb0c68773 in ?? () (gdb) # urpmf 7ed1465d37193048c31cc317564637c5d1c938 * no results *
It has a debug information in the right directory, but the build id does not match.
I think the problem is you haven't provided gdb with the executable path. Try gdb /usr/libexec/webkit2gtk-4.1/WebKitNetworkProcess core-Storage.1937.localhost.1672334056
$ gdb /usr/libexec/webkit2gtk-4.1/WebKitNetworkProcess -core core-Storage.1937.localhost.1672334056 warning: core file may not match specified executable file. Core was generated by `/usr/libexec/webkit2gtk-4.1/WebKitNetworkProcess 21 39'. -> however the backtrace looks good and the executable file is apparently the same. Possibly gdb gets irritated by the two numbers '21 39' wherever they may come from.
Status: NEW => RESOLVEDResolution: (none) => WORKSFORME