Bug 341384

Summary:	GDB will not work through KDevelop
Product:	[Applications] kdevelop	Reporter:	tedt2
Component:	CPP Debugger	Assignee:	kdevelop-bugs-null
Status:	RESOLVED WORKSFORME
Severity:	major	CC:	niko.sams
Priority:	NOR	Keywords:	triaged
Version First Reported In:	4.7.0
Target Milestone:	---
Platform:	Fedora RPMs
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description tedt2 2014-11-28 23:44:53 UTC

I have a C++ project that I use KDevelop for to build and execute.
However, 99 time out of 100 I cannot get the GDB debugger to work through KDevelop.

NOTE: I can use gdb command line debugger on this code with absolutely no problem.

I do have a SIGUSR1 timer interrupt occuring, but I turn this off using:
handle SIGUSR1 nostop noprint.
It seems I can maybe hit the first breakpoint I set and get some useful information, but usually I do not see Local or Watch variables after hitting subsequent breakpoints.
A few times I hit a breakpoint and waited quite some time to see if the local variables would show up.  I saw that after 30 seconds or so some of the variables began to show up, but this was not consistent behavior, and I was still not able to continue stepping through the code.

Overall KDevelop is a great IDE.  Sincerely, Thanks for all the hard work on this project!

Reproducible: Always

Steps to Reproduce:
1. (See above)
2.
3.

Comment 1 Milian Wolff 2014-11-30 14:12:22 UTC

Can you attach an example project that exhibits this behavior? Without a way for us to reproduce the issue, we can't do much...

Comment 2 tedt2 2014-12-01 01:12:57 UTC

I can't give out the current code that I am working on.
I will see if I can reproduce the issue with a test project.

Comment 3 Milian Wolff 2014-12-01 09:36:52 UTC

Ok, maybe it's just because of the custom signal handling. If you could try to create a test project, that would be excellent - thanks!

Comment 4 Andrew Crouthamel 2018-09-25 03:30:41 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Andrew Crouthamel 2018-10-27 02:08:05 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!