Plasmashell crash: debugging symbols

[piorunz]

Hello friends,

I've reported a plasmashell crash to bugs.kde.org. Nate Graham from KDE
has responded.

https://bugs.kde.org/show_bug.cgi?id=475779

I provided gdb reports with backtrace, however, they are not useful,
because I don't have debugging symbols for KArchive and Plasma.

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.

--
With kindest regards, Piotr.

⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system
⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org/
⠈⠳⣄⠀⠀⠀⠀

[Brad Rogers]

On Mon, 23 Oct 2023 19:19:42 +0100
piorunz <pio...@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.

--
Regards _ "Valid sig separator is {dash}{dash}{space}"
/ ) "The blindingly obvious is never immediately apparent"
/ _)rad "Is it only me that has a working delete key?"
The public wants what the public gets
Going Underground - The Jam

[piorunz]

On 23/10/2023 19:34, Brad Rogers wrote:
> On Mon, 23 Oct 2023 19:19:42 +0100
> piorunz <pio...@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.
>

No such packages in Debian:

$ aptitude search dbgsym
v libc6-dbgsym
v libc6-dbgsym:i386

Nate Graham can't help me, has expressed his dissatisfaction.
Please check the link to the bug where he commented.

[piorunz]

On 23/10/2023 19:46, Grzegorz Szymaszek wrote:
> 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
>

Hi Grzegorz,

I already have debuginfod configured, please read comments to the bug
report, link in first post. I was not able to generate meaningful
backtrace with what I have.

"or plain old debug packages"

Where I can find those?

[Grzegorz Szymaszek]

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

--
Grzegorz

[Andrey Rakhmatullin]

On Mon, Oct 23, 2023 at 08:08:56PM +0100, piorunz wrote:
> > 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,

It doesn't look like it worked then.

> "or plain old debug packages"
>
> Where I can find those?

The wiki page linked covers that too, in the "Installing the debugging symbols" section.

[Andrey Rakhmatullin]

On Mon, Oct 23, 2023 at 07:51:54PM +0100, Brad Rogers wrote:
> However, looking at the Debian packages web site indicates that debugsym
> packages are only ever in unstable
This is definitely not true.

[Cosmo]

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 😂

--
Cosmo

[Diederik de Haas]

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.

HTH,
Diederik

[piorunz]

Great, thank you!
I was able to add additional repository as you and Andrey Rakhmatullin
mentioned. And now I will get to work to install all necessary dbgsym
packages.

[piorunz]

On 23/10/2023 20:15, Andrey Rakhmatullin wrote:
> On Mon, Oct 23, 2023 at 08:08:56PM +0100, piorunz wrote:
>>> 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,
> It doesn't look like it worked then.

It's working because when I first installed it in /etc/profile, it has
downloaded some symbols for various crashing packages I stumbled upon in
the last several months. I also manually launch gdb via:

export DEBUGINFOD_URLS="https://debuginfod.debian.net" && sudo
coredumpctl debug

But it doesn't solve everything, it seems.

>> "or plain old debug packages"
>>
>> Where I can find those?
> The wiki page linked covers that too, in the "Installing the debugging symbols" section.

Thanks, indeed it does. Repo added! This, plus debuginfod, should
improve my ability to debug crashing packages.

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! I relied on this source when I first configured debuginfod,
installed gdb, and decided to have a go at it. I was not aware of any
additional repository.

[piorunz]

On 24/10/2023 09:51, 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 😂
>

Dear cosmo, I assume you are not a developer, because a developer would
not have a laugh like that from incompetency of a user who tries to
help. So if you are a Debian user, show me please how many packages and
bugs in Debian you debugged and helped to solve?

[Grzegorz Szymaszek]

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

[piorunz]

Thanks! This is my fault entirely for missing this.

Question:
Why there are two ways to obtain debugging symbols? I already have
export DEBUGINFOD_URLS="https://debuginfod.debian.net", and this failed
to resolve all problems in debugger, it seems. If debuginfod works only
partially, then it should not be recommended, I would not fall into this
trap but have added additional Debian repository instead, long time ago.

[Diederik de Haas]

On Tuesday, 24 October 2023 13:16:18 CEST piorunz wrote:
> 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.

The KDE guideline links to that Debian wiki page.
The only thing that could be improved is: 's/-dbg/-dbgsym/g'

[Cosmo]

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

--
Cosmo

[piorunz]

On 24/10/2023 12:35, Cosmo wrote:
> Dear piorunz, what do I have to do with it? You're the one who doesn't know
> what he's doing...

What you have to do with it? You are laughing at my incompetence, so I
am asking you, show my your track record, or shut up. Easy to blame
someone, not easy to prove if you are any better.

> BTW, next time ask here without going around (unintentionally) spreading
> discredit on Debian

I am reporting crashes here on Debian-KDE list very often, check my
previous posts and threads.
Only recently, due to lack of improvement with some crashing packages, I
got interested in debugging and I am achieving something.

I am still waiting for your track record, what you have done to improve
Debian?

[Diederik de Haas]

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:
- a rude, useless and possibly insulting message to the upstream maintainer
- instructing them to update the *community* *wiki* page wrt Debian
- assuming Nathan is unfamiliar with Debian "you, Mr. Graham, who doesn't know
Debian at all" (another assumption, formulated quite rudely)
- while you're factually incorrect (the KDE wiki links to the Debian wiki page
with all the needed info)

So if anything, YOU have discredited Debian.
Please refrain from doing such things in the future.

[piorunz]

On 24/10/2023 12:41, Diederik de Haas wrote:
> 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'.

Yes, for that I am sorry. I am not a developer, never written a line in
C/C++. But I am driven by the target I want to achieve (getting a crash
resolved), so every one gets better experience from using KDE, not just
me. I am not driven by my personal ego. So, cosmo can bark all day long.

> 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 (...)

Wow, things escalated very quickly! His reply to KDE bug is indeed very
rude and totally not in place!

[Diederik de Haas]

On Tuesday, 24 October 2023 13:50:25 CEST piorunz wrote:
> > Piotr didn't read/apply the whole of the Backtrace wiki page, that's their
> > only 'mistake'.
>
> Yes, for that I am sorry.

No need to apologize :) I put 'mistake' in quotes as I don't consider it a
mistake, just a step in a learning process.

[Andrey Rakhmatullin]

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",
> and this failed to resolve all problems in debugger, it seems. If
> debuginfod works only partially, then it should not be recommended

Sure, but unless someone else knows what is the cause of this problem it
looks like you need to investigate it yourself.

[piorunz]

Hi Andrey,
Thanks for your explanation. I will concentrate more on Debian
repository as a source of dbgsym packages then. I was already able to
provide more information to other unrelated crash (rasdaemon), by
sending exact, relevant backtrace to the Debian bug report. That's
thanks to your and other KDE group members help!

[Cosmo]

In data martedì 24 ottobre 2023 13:41:40 CEST, Diederik de Haas ha scritto:

> You OTOH, only sent a rude, useless and patronizing reply to this list,
> while making assumptions about someone's competence.

---snip---

> So if anything, YOU have discredited Debian.
> Please refrain from doing such things in the future.

Luckily, Mr. Graham doesn't think like you: that's because Mr. Graham is a
developer on the KDE Board of Directors; while you're just a bigoted,
frustrated priest. 😂

--
Cosmo

[Andrey Rakhmatullin]

Back to this, as I just hit the same problem I googled it and found
https://bugs.kde.org/show_bug.cgi?id=454063
So it looks like it should only work (in stable and later, which have
gdb >= 12) only if WITH_GDB12 is set at the drkonqi build time.
https://salsa.debian.org/qt-kde-team/kde/drkonqi/-/blob/master/debian/rules
doesn't set it, so I think this needs to be changed.