Bug 551288 - When debug, the Resume, Step Into, Step Over buttons greyed out
Summary: When debug, the Resume, Step Into, Step Over buttons greyed out
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug (show other bugs)
Version: 9.9.0   Edit
Hardware: PC Mac OS X
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: cdt-debug-inbox@eclipse.org CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-09-20 00:46 EDT by Gary Yang CLA
Modified: 2019-09-21 18:49 EDT (History)
2 users (show)

See Also:


Attachments
The Resume, Step in, Step over buttons greyed out (212.42 KB, image/png)
2019-09-20 00:46 EDT, Gary Yang CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gary Yang CLA 2019-09-20 00:46:25 EDT
Created attachment 279941 [details]
The Resume, Step in, Step over buttons greyed out

I use Eclipse IDE for Java Developers

Version: 2018-12 (4.10.0)
Build id: 20181214-0600

I installed CDT plugins. But, the Resume, Step in, Step over buttons greyed out when I debug the C++ code. Attached are the detailes.
Comment 1 Jonah Graham CLA 2019-09-20 14:53:21 EDT
Hi @Gary,

The reason that resume/etc are greyed out is that there is nothing selected in the Debug view that is resumable/etc. Please expand the "Debug 1 [C/C++ Application" and select a thread, process or frame.

That said, CDT should be selecting something automatically when it suspends and the fact it isn't may mean that launching is failing. If this is the case I will need some more info to be able to start to resolve. You have reported being on Mac, as your screenshot seems to match, but I don't have a Mac to try it out on. What I need to know is if GDB is working properly independent of Eclipse, or if it is the Eclipse <-> GDB integration that is failing.
Comment 2 Gary Yang CLA 2019-09-21 17:26:48 EDT
"Please expand the "Debug 1 [C/C++ Application" and select a thread, process or frame."
I clicked on the "Debug 1 [C/C++ Application". But, it does not show a thread, process or frame.

GDB is working properly independent of Eclipse. I can use it as command line debugger. How do I figure out the Eclipse <-> GDB integration that is failing? Where do I find the log?
Comment 3 Jonah Graham CLA 2019-09-21 18:49:52 EDT
The GDB MI traces are hidden by default, they can be turned on in preferences. Have a look at https://wiki.eclipse.org/CDT/User/NewIn92#Hide_gdb_traces_by_default

If you can include the traces console I can try to diagnose what has gone wrong.