kamaraju kusumanchi ha scritto: > On Thu, Dec 29, 2016 at 2:00 AM, Andrey Rahmatullin <w...@debian.org> wrote: >> On Thu, Dec 29, 2016 at 11:59:07AM +0500, Andrey Rahmatullin wrote: >>> On Thu, Dec 29, 2016 at 01:52:20AM -0500, kamaraju kusumanchi wrote: >>>> Is the above link up to date? I ask because >>>> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Debian >>>> says that there are -dbg packages that I should install to get >>>> backtrace. But I do not see any packages such as konsole-dbg or >>>> libqt5dbus5-dbg in the archive. >>> They are now konsole-dbgsym and libqt5dbus5-dbgsym. For other packages the >>> names may differ. >> You also need to enable the debug repo, see >> https://wiki.debian.org/AutomaticDebugPackages > > Thanks. Just for the record, I also found > https://wiki.debian.org/HowToGetABacktrace to be useful for this > exercise. Here is the backtrace with all the symbols. > > > % gdb konsole > ... > Reading symbols from konsole...Reading symbols from > /usr/lib/debug/.build-id/2b/559c27a0259b9f5254ac6482a73ecd5f0fce6a.debug...done. > done. > (gdb) set args --version > (gdb) r > Starting program: /usr/bin/konsole --version > [Thread debugging using libthread_db enabled] > Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". > [New Thread 0x7fffe414b700 (LWP 23997)] > [New Thread 0x7fffe2268700 (LWP 23998)] > konsole 16.08.2 >
When the backtrace starts, do you get the prompt of (gdb) again? Try to type: (gdb) thread apply all backtrace and see if it gives you more output. Just to be sure: did you restart after the last updates (not only kernel, also Qt)? -- Luigi
