Can anyone tell me, how to obtain debugging symbols for KDE, so I can >backtrace a crash with debugger properly? I use Debian Stable. Thank
you.
On Mon, 23 Oct 2023 19:19:42 +0100
piorunz <piorunz@gmx.com> wrote:
Hello piorunz,
Can anyone tell me, how to obtain debugging symbols for KDE, so I can
backtrace a crash with debugger properly? I use Debian Stable. Thank
you.
Search for packages with -dbgsym at the end. If unsure which one(s), ask Nate - I'm sure they won't mind.
Hi,
On Mon, Oct 23, 2023 at 07:19:42PM +0100, piorunz wrote:
Can anyone tell me, how to obtain debugging symbols for KDE, so I can
backtrace a crash with debugger properly? I use Debian Stable. Thank you.
In general, assuming you use KDE packages from official Debian archives,
you can use either debuginfod, or plain old debug packages. Have a look
at the Wiki: HowToGetABacktrace[1]. It includes some hints on how to
obtain the needed debug package names. Let us know if you'll have
further issues or if there's something to improve in that Wiki text.
[1]: https://wiki.debian.org/HowToGetABacktrace
In general, assuming you use KDE packages from official Debian archives, you can use either debuginfod, or plain old debug packages. Have a look
at the Wiki: HowToGetABacktrace[1]. It includes some hints on how to
obtain the needed debug package names. Let us know if you'll have
further issues or if there's something to improve in that Wiki text.
[1]: https://wiki.debian.org/HowToGetABacktrace
Hi Grzegorz,It doesn't look like it worked then.
I already have debuginfod configured,
"or plain old debug packages"The wiki page linked covers that too, in the "Installing the debugging symbols" section.
Where I can find those?
However, looking at the Debian packages web site indicates that debugsym packages are only ever in unstableThis is definitely not true.
Can anyone tell me, how to obtain debugging symbols for KDE, so I can backtrace a crash with debugger properly? I use Debian Stable. Thank you.
#2 0x00007fe7678a8e9b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4e9b)
This KDE guideline should definitely be improved: https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Debian
It doesn't say anything about additional debugging repository available
in Debian! [...]
On Monday, 23 October 2023 20:19:42 CEST piorunz wrote:
Can anyone tell me, how to obtain debugging symbols for KDE, so I can
backtrace a crash with debugger properly? I use Debian Stable. Thank you.
Add the following line to your /etc/apt/sources.list and do `apt update`
deb http://debug.mirrors.debian.org/debian-debug bookworm-debug main non-free-firmware
Then you will find the dbgsym packages.
#2 0x00007fe7678a8e9b _ZN6KCrash15setCrashHandlerEPFviE (libKF5Crash.so.5 + 0x4e9b)
With `apt-file search libKF5Crash.so.5` you'll find it belongs to the libkf5crash5 package and then do `aptitude search libkf5crash5` and you should
find a package with a `-dbgsym` suffix and you install that package.
Repeat that for all the libraries in your stacktrace and when you then generate
a new stacktrace, it should contain all the info you want/need.
piorunz is so incompetent that he managed to discredit the whole of Debian in front of one of the prominent kde project managers. Nice job 😂
On Mon, Oct 23, 2023 at 08:08:56PM +0100, piorunz wrote:
It doesn't look like it worked then.In general, assuming you use KDE packages from official Debian archives, >>> you can use either debuginfod, or plain old debug packages. Have a look
at the Wiki: HowToGetABacktrace[1]. It includes some hints on how to
obtain the needed debug package names. Let us know if you'll have
further issues or if there's something to improve in that Wiki text.
[1]: https://wiki.debian.org/HowToGetABacktrace
Hi Grzegorz,
I already have debuginfod configured,
"or plain old debug packages"The wiki page linked covers that too, in the "Installing the debugging symbols" section.
Where I can find those?
On 24/10/2023 12:03, Grzegorz Szymaszek wrote:
On Tue, Oct 24, 2023 at 11:57:46AM +0100, piorunz wrote:
This KDE guideline should definitely be improved:
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_u >> seful_crash_reports#Debian
It doesn't say anything about additional debugging repository available
in Debian! [...]
"See also the Debian document on How to get a Backtrace." links to https://wiki.debian.org/HowToGetABacktrace
Thanks! This is my fault entirely for missing this.
On Tue, Oct 24, 2023 at 11:57:46AM +0100, piorunz wrote:
This KDE guideline should definitely be improved:
https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Debian
It doesn't say anything about additional debugging repository available
in Debian! [...]
"See also the Debian document on How to get a Backtrace." links to https://wiki.debian.org/HowToGetABacktrace
Dear piorunz, what do I have to do with it? You're the one who doesn't know what he's doing...
BTW, next time ask here without going around (unintentionally) spreading discredit on Debian
piorunz is so incompetent that he managed to discredit the whole of Debian
in front of one of the prominent kde project managers. Nice job 😂
On Tuesday, 24 October 2023 10:51:46 CEST Cosmo wrote:
piorunz is so incompetent that he managed to discredit the whole of Debian >> in front of one of the prominent kde project managers. Nice job 😂
Piotr didn't read/apply the whole of the Backtrace wiki page, that's their only 'mistake'.
You OTOH, only sent a rude, useless and patronizing reply to this list, while making assumptions about someone's competence.
If that wasn't bad enough, you also added to the upstream bug report (...)
Why there are two ways to obtain debugging symbols?The -dbgsym packages is the official method since its introduction,
I already have export DEBUGINFOD_URLS="https://debuginfod.debian.net",Sure, but unless someone else knows what is the cause of this problem it
and this failed to resolve all problems in debugger, it seems. If
debuginfod works only partially, then it should not be recommended
Piotr didn't read/apply the whole of the Backtrace wiki page, that's their only 'mistake'.
Yes, for that I am sorry.
On Tue, Oct 24, 2023 at 12:16:18PM +0100, piorunz wrote:
Why there are two ways to obtain debugging symbols?The -dbgsym packages is the official method since its introduction, debuginfod is newer and has some downsides, e.g. it's easier to
pre-install all -dbgsym you could need and not worry about downloading symbols on demand.
I already have export DEBUGINFOD_URLS="https://debuginfod.debian.net",Sure, but unless someone else knows what is the cause of this problem it looks like you need to investigate it yourself.
and this failed to resolve all problems in debugger, it seems. If
debuginfod works only partially, then it should not be recommended
You OTOH, only sent a rude, useless and patronizing reply to this list,---snip---
while making assumptions about someone's competence.
So if anything, YOU have discredited Debian.
Please refrain from doing such things in the future.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 307 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 134:59:28 |
| Calls: | 6,857 |
| Calls today: | 3 |
| Files: | 12,360 |
| Messages: | 5,418,393 |