Re: drkonqi integration

As in, the DrKonqi backtrace collection button or the Kdevelop debugger?

I lurk in the mailing list a bit and, as an end user, I did frequently use =
the DrKonqi button to save backtraces so I could possibly report them later=
. And as someone currently trying to learn C, if you meant remivung a butto=
n to use GDB in Kdevelop, I'd just drop Kdevelop entirely (as a user) becau=
se Kdevelop already throws me a few frustrations as an IDE (on Gentoo) and =
I just wouldn't tolerate an IDE without an included debugger. That's just m=
y two-cents though, to answer your question... Not entirely sure if I did a=
dequately, though.


-------- Original Message --------
On 7/27/24 8:02 AM, Christoph Roick <[email protected]> wrote:

>  Am Freitag, 26. Juli 2024, 17:40:02 MESZ schrieb Igor Kushnir:
>  > On 2024-07-25 12:11 PM, Harald Sitter wrote:
>  > > Yo
>  > >
>  > > there is this pile of code that lets kdevelop interface with drkonqi
>  > > to hand over the debugging from drkonqi into kdevelop. it currently
>  > > has no UI backing in 6 and also doesn't really work with the default
>  > > coredumpd-based crash handling
>  > >
>  > > I am wondering how sad we would be if we just threw away the code?
>  > >
>  > > At a glance we could remove
>  > >
>  > > - the entire socket tech in kcrash
>  > > https://invent.kde.org/frameworks/kcrash/-/blob/master/src/kcrash.cp=
p?ref_type=3Dheads#L799
>  > > - the external debugger tech in drkonqi
>  > > https://invent.kde.org/plasma/drkonqi/-/blob/master/src/debuggerlaun=
chers.h?ref_type=3Dheads
>  > > - dbus interaction code in kdevelop
>  > > https://invent.kde.org/kdevelop/kdevelop/-/blob/master/plugins/debug=
gercommon/midebuggerplugin.cpp#L135
>  > >
>  > > HS
>  >
>  > Hi everyone!
>  >
>  > Adding the author of the most recent work on this integration:
>  > https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/202
>  >
>  > Christoph, would you like to fix the DrKonqi integration again, now or=
 in the
>  > future? If you don't have motivation or time for this, before removing=
 it all,
>  > we need to consider how difficult fixing the integration will be and h=
ow often
>  > it is used. As the integration only broke recently, perhaps wait for b=
ug reports
>  > about it against KDevelop 6.0?
>  >
>  > Cheers,
>  > Igor
> =20
>  Hi,
> =20
>  Actually the button that featured launching the debugger does not show u=
p,
>  since QML is put in place for DrKonqi. That's the case for some time now=
.
>  Should be effective since commit 61e4560e (grand qml UI rewrite) from '2=
2.
>  If anybody missed the button, there should have been bug reports already=
.
> =20
>  I liked investigating crashes quickly when they appeared, but lost the m=
otivation
>  to do so since the button was gone. I think only a handful of people (ma=
ybe just
>  me) used the feature however. So cleaning that up would probably be the =
better
>  choice to reduce complexity. Especially considering the effort it takes =
to revive
>  the feature (together with the opt-in gdb debug possibility that nobody =
knows
>  about).
> =20
>  Rephrasing Haralds question: Would anybody in this mailing list like to =
see the
>  button again?
> =20
>  Best regards
>  Christoph
> =20
> =20
> =20
>