<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">To avoid some confusion:</p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">It's not about removing debugging from KDevelop. There used to be a button in</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">DrKonqi that would allow you to attach a crashed application to a new debug session</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">in one of the running KDevelop sessions (depending on which debuggers are set up,</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">gdb and lldb in my case) or, if enabled in the DrKonqi configuration, directly to one of</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">the installed debuggers. By default the button was only displayed if KDevelop was</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">runnning or you started KDevelop while the crash window was being displayed.</p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">There are some screenshots in this discussion: <a href="https://phabricator.kde.org/D11234">https://phabricator.kde.org/D11234</a></p>
<br /><p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">Am Samstag, 27. Juli 2024, 17:19:54 MESZ schrieb Neko-san:</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> As in, the DrKonqi backtrace collection button or the Kdevelop debugger?</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> </p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> 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 button to use GDB in Kdevelop, I'd just drop Kdevelop entirely (as a user) because 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 my two-cents though, to answer your question... Not entirely sure if I did adequately, though.</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> </p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> </p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> -------- Original Message --------</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> On 7/27/24 8:02 AM, Christoph Roick <chrisito@gmx.de> wrote:</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> </p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > Am Freitag, 26. Juli 2024, 17:40:02 MESZ schrieb Igor Kushnir:</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > On 2024-07-25 12:11 PM, Harald Sitter wrote:</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > > Yo</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > ></p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > > there is this pile of code that lets kdevelop interface with drkonqi</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > > to hand over the debugging from drkonqi into kdevelop. it currently</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > > has no UI backing in 6 and also doesn't really work with the default</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > > coredumpd-based crash handling</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > ></p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > > I am wondering how sad we would be if we just threw away the code?</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > ></p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > > At a glance we could remove</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > ></p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > > - the entire socket tech in kcrash</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > > https://invent.kde.org/frameworks/kcrash/-/blob/master/src/kcrash.cpp?ref_type=heads#L799</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > > - the external debugger tech in drkonqi</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > > https://invent.kde.org/plasma/drkonqi/-/blob/master/src/debuggerlaunchers.h?ref_type=heads</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > > - dbus interaction code in kdevelop</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > > https://invent.kde.org/kdevelop/kdevelop/-/blob/master/plugins/debuggercommon/midebuggerplugin.cpp#L135</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > ></p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > > HS</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > ></p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > Hi everyone!</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > ></p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > Adding the author of the most recent work on this integration:</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > https://invent.kde.org/kdevelop/kdevelop/-/merge_requests/202</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > ></p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > Christoph, would you like to fix the DrKonqi integration again, now or in the</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > future? If you don't have motivation or time for this, before removing it all,</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > we need to consider how difficult fixing the integration will be and how often</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > it is used. As the integration only broke recently, perhaps wait for bug reports</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > about it against KDevelop 6.0?</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > ></p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > Cheers,</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > > Igor</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > </p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > Hi,</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > </p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > Actually the button that featured launching the debugger does not show up,</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > since QML is put in place for DrKonqi. That's the case for some time now.</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > Should be effective since commit 61e4560e (grand qml UI rewrite) from '22.</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > If anybody missed the button, there should have been bug reports already.</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > </p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > I liked investigating crashes quickly when they appeared, but lost the motivation</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > to do so since the button was gone. I think only a handful of people (maybe just</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > me) used the feature however. So cleaning that up would probably be the better</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > choice to reduce complexity. Especially considering the effort it takes to revive</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > the feature (together with the opt-in gdb debug possibility that nobody knows</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > about).</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > </p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > Rephrasing Haralds question: Would anybody in this mailing list like to see the</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > button again?</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > </p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > Best regards</p>
<p style="margin-top:0;margin-bottom:0;margin-left:0;margin-right:0;">> > Christoph</p>
</body>
</html>