Bug 338287 - Kdevelop crashes when tryig to debug with external window
Summary: Kdevelop crashes when tryig to debug with external window
Status: RESOLVED FIXED
Alias: None
Product: kdevelop
Classification: Applications
Component: general (other bugs)
Version First Reported In: 4.6.1
Platform: Kubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-15 02:32 UTC by Ekkehard Blanz
Modified: 2018-11-13 19:26 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments
crash assistant generated (18.06 KB, text/plain)
2014-08-15 02:32 UTC, Ekkehard Blanz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ekkehard Blanz 2014-08-15 02:32:18 UTC
Created attachment 88263 [details]
crash assistant generated

I am having a hell of a time trying to get Kdevelop working again with gdb (haven't used it in about a year).  To test it out, I tried a simple hello world program with a two-line Makefile.  When I start the Debug process, the debug screen comes up for a few milliseconds and then throws me back into the Coding screen.  Starting gdb with a CLI on its own works fine.  To debug the problem, I tried to use an external terminal (konsole --noclose --workdir %workdir -e %exe) in the launch configuration as both the "Debug" and the "GDB" tabs are empty.  When I then started the debugger within Kdevelop again, it crashed.

gdb version is 7.7, Distro is Kubuntu 14.04, rest should be in the attached report
Comment 1 Andrew Crouthamel 2018-11-12 02:53:14 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Ekkehard Blanz 2018-11-13 19:26:51 UTC
Just re-tested it.  My current distro (Kubuntu 18.04 LTS) version (5.2.1) does not exhibit this bug anymore.  As far as I am concerned, this bug appears to be fixed and the case can be closed.