Home » Language IDEs » C / C++ IDE (CDT) » Cannot Start Debugger
| Cannot Start Debugger [message #116585] |
Mon, 23 August 2004 12:00  |
Eclipse User |
|
|
|
Originally posted by: davidwarndt.hotmail.com
Help. The "Debug" button in Eclipse is permanently grayed out. I can
launch my application by double clicking it from the folder list, but if I
try to select it for debugging, Eclipse is telling me that it's "not a valid
binary". What might I be doing wrong?
I've also duplicated this problem on two different machines. Here's the
environment:
Windows 2000
GNU C++ (g++) (latest Cygwin download)
CDT 2.0 under Eclipse
GDB debugger selected
I submitted a bugzilla report, but as usual just got back a snotty reply
from someone who summarily marked the report is 'invalid'. Big help.
What might I be doing wrong?
-- da
|
|
|
| Re: Cannot Start Debugger [message #116711 is a reply to message #116585] |
Mon, 23 August 2004 13:23  |
| Eclipse User |
|
|
|
David,
There have been numerous variations on this theme on this newsgroup. I
am going to ask the basic question I ask everyone else with this
problem. Do you have the right binary parser set for the project? If
not, the CDT will not recognize the the build goal as a program and
therefore, you will never be able to select it in the debugger. This is
a problem for people running MacOS, so it frequently appears as a
question with that in the title. If you are building a standard Windows
executable using the GCC tools in Cygwin, then the Cygwin PE parser
should be sufficient. If you have the right parser set, can you debug
your program with gdb/ddd manually? Hope this helps point you in the
right direction.
Sean
David Arndt wrote:
> Help. The "Debug" button in Eclipse is permanently grayed out. I can
> launch my application by double clicking it from the folder list, but if I
> try to select it for debugging, Eclipse is telling me that it's "not a valid
> binary". What might I be doing wrong?
>
> I've also duplicated this problem on two different machines. Here's the
> environment:
>
> Windows 2000
> GNU C++ (g++) (latest Cygwin download)
> CDT 2.0 under Eclipse
> GDB debugger selected
>
> I submitted a bugzilla report, but as usual just got back a snotty reply
> from someone who summarily marked the report is 'invalid'. Big help.
>
> What might I be doing wrong?
>
> -- da
>
>
|
|
|
| Re: Cannot Start Debugger [message #116722 is a reply to message #116711] |
Mon, 23 August 2004 13:41 |
| Eclipse User |
|
|
|
"Sean Evoy" <sevoy@ca.ibm.com> wrote in message
news:cgd91g$19d$1@eclipse.org...
> David,
> There have been numerous variations on this theme on this newsgroup. I
> am going to ask the basic question I ask everyone else with this
> problem. Do you have the right binary parser set for the project? If
> not, the CDT will not recognize the the build goal as a program and
> therefore, you will never be able to select it in the debugger. This is
> a problem for people running MacOS, so it frequently appears as a
> question with that in the title. If you are building a standard Windows
> executable using the GCC tools in Cygwin, then the Cygwin PE parser
> should be sufficient. If you have the right parser set, can you debug
> your program with gdb/ddd manually? Hope this helps point you in the
> right direction.
>
Thanks, Shawn. Since I posted, I realized (with the help of a colleque)
that if I specify "Executable - Cygwin" instead of "Executable - GNU", when
I create the project, I'm able to debug.
Is this where you set the 'binary parser'? I don't see anywhere else after
project creation to control this option. The other thing that is
confusing, is that the GNU tools I'm using were downloaded *with* Cygwin -
so I'm confused about the difference between selecting "Executable - Cygwin"
vs. "Executable - GNU"? At first, I selected the later, because I
reasoned that the executable wasn't intended for running under Cygwin, per
se, but just a plain vanilla executable to be run under Windows straight
out. But apparently, there's some distiction.
I'm obviously not understanding the "Eclipse" terminology. I have tried
reading the help docs and searching via google and other newsgroups - but
haven't been able to gleen the info that I need. So, I apologize if this
comes off as an annoying or newbie type question.
The next problem I'm running into is that I can't figure out how to load the
symbols for a .SO, so that I can step into a DLL call. I saw a note on
another thread that you should be able to go into assembly mode and step
through the thunk, but I haven't been able to get this to work either.
Can you sort this out for us?
-- da
|
|
|
| Re: Cannot Start Debugger [message #116734 is a reply to message #116722] |
Mon, 23 August 2004 13:55 |
| Eclipse User |
|
|
|
David,
For an existing managed project, the binary parser can be changed/set
via the Properties->Error/Binary Parser->Binary Parser tab. The parser
is set by default based on the target you select in the new project
wizard. You can hide the targets that are not appropriate for your OS by
deselecting the 'Show all' option in the wizard.
The reason we have to distinguish between the GCC tools on Cygwin vs.
GCC tools on POSIX systems is that there are subtle but important
differences in what gets built by various build goals and how the paths
are dealt with. For now, the simplest solution is to treat Cygwin as a
specialized case of a GCC build target.
Since you have found the thread on stepping into DLLs, I will assume
that you already have compiled the DLLs with debugging symbols in them
and know whereof you speak. I just build 'em; debugging is not my area
of expertise, so I will leave that to others to help you with.
I will try to condense your experience into an entry in the README,
since you have encountered a 'gotcha' I did not anticipate, it could
easily happen to other people, and there is a solution.
Sean
David Arndt wrote:
> "Sean Evoy" <sevoy@ca.ibm.com> wrote in message
> news:cgd91g$19d$1@eclipse.org...
>
>>David,
>>There have been numerous variations on this theme on this newsgroup. I
>>am going to ask the basic question I ask everyone else with this
>>problem. Do you have the right binary parser set for the project? If
>>not, the CDT will not recognize the the build goal as a program and
>>therefore, you will never be able to select it in the debugger. This is
>>a problem for people running MacOS, so it frequently appears as a
>>question with that in the title. If you are building a standard Windows
>>executable using the GCC tools in Cygwin, then the Cygwin PE parser
>>should be sufficient. If you have the right parser set, can you debug
>>your program with gdb/ddd manually? Hope this helps point you in the
>>right direction.
>>
>
>
> Thanks, Shawn. Since I posted, I realized (with the help of a colleque)
> that if I specify "Executable - Cygwin" instead of "Executable - GNU", when
> I create the project, I'm able to debug.
>
> Is this where you set the 'binary parser'? I don't see anywhere else after
> project creation to control this option. The other thing that is
> confusing, is that the GNU tools I'm using were downloaded *with* Cygwin -
> so I'm confused about the difference between selecting "Executable - Cygwin"
> vs. "Executable - GNU"? At first, I selected the later, because I
> reasoned that the executable wasn't intended for running under Cygwin, per
> se, but just a plain vanilla executable to be run under Windows straight
> out. But apparently, there's some distiction.
>
> I'm obviously not understanding the "Eclipse" terminology. I have tried
> reading the help docs and searching via google and other newsgroups - but
> haven't been able to gleen the info that I need. So, I apologize if this
> comes off as an annoying or newbie type question.
>
> The next problem I'm running into is that I can't figure out how to load the
> symbols for a .SO, so that I can step into a DLL call. I saw a note on
> another thread that you should be able to go into assembly mode and step
> through the thunk, but I haven't been able to get this to work either.
>
> Can you sort this out for us?
>
> -- da
>
>
|
|
|
| Re: Cannot Start Debugger [message #116879 is a reply to message #116734] |
Tue, 24 August 2004 09:14 |
| Eclipse User |
|
|
|
>
> Since you have found the thread on stepping into DLLs, I will assume
> that you already have compiled the DLLs with debugging symbols in them
> and know whereof you speak. I just build 'em; debugging is not my area
> of expertise, so I will leave that to others to help you with.
>
Well, this is my next hurdle. I've got DLLs (.so's) with debugging symbols,
but I've had NO luck at all getting Eclipse to run the debugger and set
breakpoint inside the .so's. It (either CDT or Eclipse) seems to be VERY
buggy. One would think this would be a very straight forward and essential
task to make transparent - but I'm probably spoiled!
Do you know if there are any articles or examples of doing this successfully
under Eclipse/CDT?
> I will try to condense your experience into an entry in the README,
> since you have encountered a 'gotcha' I did not anticipate, it could
> easily happen to other people, and there is a solution.
>
Thanks, again!
-- Dave
|
|
|
Goto Forum:
Current Time: Thu Jun 05 02:18:53 EDT 2025
Powered by FUDForum. Page generated in 0.05385 seconds |
Home