Re: Testing back traces

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

 



On 5/4/25 8:28 AM, Michele Calgaro via tde-devels wrote:
I am creating a Slackware build environment. I want to test back traces (not tripping out symbols).

I seem to recall there was a way to test this in TDE but I don't remember. How to test back traces and symbols?

what exactly do you mean by "testing a backtrace"?

I seem to recall there was a way to force a crash that invoked the drkonqi dialog to create a back trace.

My new Slackware build environment (112 packages so far compiled :)) has the option to include symbols. I want to test that is functioning so my packages can provide helpful back traces.

Some minutes ago I discovered a file called crashtest installed from tdebase, but I haven't tested. Maybe that is what I am looking for?
____________________________________________________
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