[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: drkonqi's many debuggers
From:       Thiago Macieira <thiago () kde ! org>
Date:       2023-08-29 5:11:01
Message-ID: 8306929.NyiUUSuA9g () tjmaciei-mobl5
[Download RAW message or body]

On Monday, 28 August 2023 21:33:25 PDT Nate Graham wrote:
> On 8/28/23 22:25, Thiago Macieira wrote:
> > It does because it might be missing in the system far more often than gdb.
> > We'd get more backtraces and therefore more data if we focused on gdb
> > 
> > Another point is that Linux distributions have been shipping gdb with
> > debuginfod support for a year or two. lldb support for it is still
> > pending:
> > https://github.com/llvm/llvm-project/issues/52732
> > 
> > Therefore, I repeat: if there's room for only one, it's gdb.
> > 
> > If we do support both, then on Linux gdb must be used in preference.
> 
> DrKonqi itself could declare a required build dependency on lldb, and
> then we would know it's present on the system. Distros that don't
> package it would then have to omit DrKonqi, or start packaging it.

Build dependencies don't necessarily translate to runtime dependencies. What 
you're asking for is package management, something we don't control. Yes, we 
could convince all packagers to add it, but

a) that's not a sure-fire guarantee
b) do we even want to? Do we want to make it so every user who installs Plasma 
Workspace must have a debugger?

No, debuggers are optional.

Then there's my argument about libdebuginfo integration.

-- 
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
   Software Architect - Intel DCAI Cloud Engineering



[prev in list] [next in list] [prev in thread] [next in thread]