Bug 134827 - Debug / Debugging options are disabled
Summary: Debug / Debugging options are disabled
Status: RESOLVED NOT A BUG
Alias: None
Product: kdevelop
Classification: Applications
Component: CPP Debugger (show other bugs)
Version: 3.3.92
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: kdevelop-bugs-null
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-29 09:37 UTC by Syam
Modified: 2007-01-04 06:05 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Syam 2006-09-29 09:37:03 UTC
Version:           3.3.92 (using KDE KDE 3.5.3)
Installed from:    Compiled From Sources
Compiler:          gcc 4.1.1 gcc (GCC) 4.1.1 20060525 (Red Hat 4.1.1-1)
OS:                Linux

I compiled KDevelop 3.3.92 from sources from KDevelop website. I am doing a qmake project. I am able to set breakpoints and start the debugger. The program runs, and stops at the breakpoint as expected. But the problem is that the Step over, step into etc. buttons (and menu items) are disabled. The 'interrupt' option is enabled, but there's no effect.

Due to the above issue, I am unable to debug.

I tried creating a simple hello world c++ app, and by changing 'debugging shell' from 'libtool' to empty and by entering gdb path in debugger path, I am able to debug.
Comment 1 Syam 2006-09-30 04:16:48 UTC
Some additional info:
The qmake project I was referring to, was not created using this version of KDevelop. I was previously using the stable KDevelop 3.3 version and debugging worked fine.
Now I have compiled 3.3.92 and opened the same project file.
Comment 2 Syam 2006-09-30 04:20:29 UTC
Additional info: gdb version: GNU gdb Red Hat Linux (6.3.0.0-1.122rh)
Comment 3 Syam 2006-09-30 05:12:49 UTC
Update: I installed gdb 6.4. Now debugging works and I am able to step over step in to etc. But now gdb (and KDevelop) crashes when I close my running application after debugging.

The series of messsages displayed:

1. 'Debugger error', Debugger reported the following error:, Couldn't get registers: No such process.

2. 'Debugger error', Debugger reported the following error:,Cannot fetch general-purpose registers for thread -1208752432: generic error

3. 'Debugger error', Debugger reported the following error:,Cannot fetch general-purpose registers for thread -1208752432: generic error

4. The debugger component encountered internal error while processing reply from gdb. Please submit a bug report.
    Details>> The exception is: MI type error. The MI response is: ^done

And after that, Kdevelop CRASHES (SIGABRT).

My application is multithreaded and uses 3 threads.
Comment 4 Vladimir Prus 2006-10-14 16:37:46 UTC
Can you please provide the complet project on which the problem is happening. Also, in "crashes when I close my running application after debugging" what is "closing". What buttons/menu items do you use, specifically?
Comment 5 Jens Dagerbo 2007-01-04 06:05:30 UTC
Here's a report that solved itself and turned into a new report that's missing information and no reply from the reporter for 2 months.

It's not much use, and from the brief description it's probably a dupe. Closing.