On Sunday 04 May 2025 20:34:49 Darrell Anderson via tde-devels wrote: > 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. just send a SIGABRT to a tde process and you probably will see what you want. (kill -6) This signal calls abort() for any process. > > 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@trinitydesk >top.org ____________________________________________________ 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
