https://bugs.kde.org/show_bug.cgi?id=346118
--- Comment #148 from white...@gmail.com ---
(In reply to madcatx from comment #147)
> You need both qt5-declarative and plasma-nm package built with debugging
> symbols to get a useful backtrace. Are you sure you set options=("!strip")
> in plasma-nm's PKGBUILD? Without it the debugging symbols get stripped away.
> I'm not sure what is the point to run gdb through codedumpctl, running just
> plain gdb worked perfectly fine for me.
Thanks for reply.
plasma-nm is not stripped:
/usr/lib/libplasmanm_internal.so: ELF 64-bit LSB shared object, x86-64, version
1 (GNU/Linux), dynamically linked,
BuildID[sha1]=dbdc42f144e99d59f1e83c1b331bcf50234db6cc, not stripped
qt is not stripped:
/usr/lib/libQt5Gui.so.5.7.0: ELF 64-bit LSB shared object, x86-64, version 1
(GNU/Linux), dynamically linked,
BuildID[sha1]=62cb08d718d538911260b1462f9f5b34dcdd4b94, not stripped
qt5-declarative is not stripped
/usr/lib/libQt5Qml.so.5.7.0: ELF 64-bit LSB shared object, x86-64, version 1
(GNU/Linux), dynamically linked,
BuildID[sha1]=849296eda22a1f1d6ef416f95b8983efdf9bd8f4, not stripped
anyway I still see no backtrace.
Could you help me using gdb directly without coredumpctl?
--
You are receiving this mail because:
You are watching all bug changes.
