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.
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
On 24/10/2023 13:57, Andrey Rakhmatullin wrote:
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
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
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
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
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
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
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
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:
> >>
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_useful_crash_reports#Debian
It doesn't say anything about additional
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
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
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
On 24/10/2023 11:36, Diederik de Haas wrote:
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
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
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
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.
On Mon, 23 Oct 2023 19:19:42 +0100
piorunz 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.
Okay, I've now had a chance to read the bug report. I've just made
things
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
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
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
On 23/10/2023 19:34, Brad Rogers wrote:
On Mon, 23 Oct 2023 19:19:42 +0100
piorunz 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
On Mon, 23 Oct 2023 19:19:42 +0100
piorunz 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 -
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
25 matches
Mail list logo
