Summary: | kde-apps/dolphin - Drag 'n Dropping Crashes File Manager (LLVM profile) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Neko-san <gentoo.qxrin> |
Component: | Current packages | Assignee: | Gentoo KDE team <kde> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
Build Log
Dolphin GDB Tee'd Output Log Dr Konqi Kcrash Log Backtrace Backtrace Backtrace |
Description
Neko-san
2023-09-18 20:45:39 UTC
Created attachment 870896 [details]
Build Log
Could you get us a backtrace please when it crashes? See https://wiki.gentoo.org/wiki/Debugging#Per-package. I was worried you'd ask that; I don't have debugging *at all* at the moment and I imagine for me to give you a useful backtrace, I'd probably have to rebuild... I don't know how many things Also, correction on my end: it seems to be if you attempt dragging a file into the address bar; the address bar and folder tabs are nearby each other so I mis-interpreted what was actually causing the crash (In reply to Neko-san from comment #3) > I was worried you'd ask that; I don't have debugging *at all* at the moment > and I imagine for me to give you a useful backtrace, I'd probably have to > rebuild... I don't know how many things I'd just do Dolphin first, then can go off the backtrace to see what else needs debugging symbols built. ...but please also report back with all latest versions of dev-qt/*:5, kde-frameworks/* and kde-apps/dolphin upgraded. Created attachment 872125 [details]
Dolphin GDB Tee'd Output Log
Created attachment 872126 [details]
Dr Konqi Kcrash Log
I used "splitdebug compressdebug -nostrip" and rebuilt my entire @world and then tried to collect a backtrace (In reply to Neko-san from comment #6) > Created attachment 872125 [details] > Dolphin GDB Tee'd Output Log Thread 1 "dolphin" received signal SIGSEGV, Segmentation fault. 0x00007ffff7e178c2 in ?? () from /usr/lib64/libKF5KIOFileWidgets.so.5 (gdb) continue Continuing. Please do 'bt' at that point instead of 'continue'. (In reply to Neko-san from comment #8) > I used "splitdebug compressdebug -nostrip" and rebuilt my entire @world and > then tried to collect a backtrace Using -ggdb3 too, or similar, as well, with debugedit installed? I used -ggdb3 but I didn't have debugedit installed (I didn't even know that package existed because I didn't notice a reference to it anywhere) Created attachment 872195 [details]
Backtrace
Is this better?
Created attachment 872196 [details]
Backtrace
(In reply to Neko-san from comment #10) > I used -ggdb3 but I didn't have debugedit installed (I didn't even know that > package existed because I didn't notice a reference to it anywhere) It's mentioned at https://wiki.gentoo.org/wiki/Debugging#Per-package. (In reply to Neko-san from comment #12) > Created attachment 872196 [details] > Backtrace Yeah, this is a lot better. You need to rebuild a lot of the mentioned libraries on the right hand side though, like /usr/lib64/libKF5KIOFileWidgets.so.5, /usr/lib64/libQt5Widgets.so.5, etc. (You can do: emerge -v1 /path/to/lib as long as you configured the debug symbols env first.) > It's mentioned at https://wiki.gentoo.org/wiki/Debugging#Per-package.
Ah, I missed the part where it says to use the "installsources" feature too...; oops
Created attachment 872248 [details]
Backtrace
I had to stop using splitdebug and just use nostrip because no variation of the splitdebug setup was showing the missing symbols, so I did that, and ran:
emerge -v1 /usr/lib64/libKF5KIOFileWidgets.so.5 /usr/lib64/libQt5Widgets.so.5 /usr/lib64/libQt5XcbQpa.so.5 /usr/lib64/libglib-2.0.so.0 kde-apps/dolphin
The backtrace seems to have a lot more information now, but I don't understand why it wouldn't find the symbols before :/
Very weird - it might be because Clang uses dwarf5 by default which debugedit doesn't support yet. But that backtrace you just posted looks perfect - thank you! Does it still happen if you build Qt with some more vanilla flags? (try just -O2 -march=native first) Qt 5 is extremely sensitive and likely has a bunch of UB so it's wise to build it with conservative flags Rebuilding dev-qt/qtcore, dev-qt/qtgui, dev-qt/qtwidgets that way seems to still reproduce the issue, yeah What about newer versions? Qt has been updated to 5.15.11 in stable, kde-apps/dolphin-23.08.3 is close. It's still reproducible, yeah @SamJames, by the way, do you know when debugedit will support that? And do you think building my packages with the symbols just built in going further (until that gets supported) would be too much of a storage or performance issue? (My machine runs on a 250 GB SSD and it only has 55 GBs of space left (partially because I have one somewhat large game installed on it also) |