Re: kdDebug on the fly

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2022/10/09 07:38 AM, deloptes wrote:
Michele Calgaro via tde-devels wrote:

first of all, kdDebug and debug symbols are two independent concepts.
dbgsym are symbols that can be used when debugging the program within a
debugger like gdb. kdDebug is a stream object that let you print messages
to a stream, regardless of whether you have installed debug symbols or
not.

in this context, what is DrKonqi using to display the debug?
I do not see there the backtrace, when it crashes so what should I do to see
it (when I run the application from the place it was build)


DrKonqui uses a backtrace, pretty much capturing the same info you would see in gdb when looking at the backtrace after a crash. If you have debug symbols installed, those will be used to display additional info about the crash (either by DrKonqui or gdb). There is a kdBacktrace() function in kdebug.cpp in tdelibs which builds a backtrace. You can print a backtrace programmatically even without a crash by using it in your code.
Cheers
  Michele

Attachment: OpenPGP_signature
Description: OpenPGP digital signature

____________________________________________________
tde-devels mailing list -- devels@xxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devels-leave@xxxxxxxxxxxxxxxxxx
Web mail archive available at https://mail.trinitydesktop.org/mailman3/hyperkitty/list/devels@xxxxxxxxxxxxxxxxxx

[Index of Archives]     [Trinity Users]     [Linux Sound]     [ALSA Users]     [ALSA Devel]     [Linux Audio Users]     [Linux Media]     [KDE]     [Kernel]     [Gimp]     [Yosemite News]     [Linux Media]     [Trinity Desktop Environment]

  Powered by Linux