| Debugging standard C app via Cygwin [message #143792] |
Fri, 22 April 2005 09:46  |
Eclipse User |
|
|
|
Originally posted by: overbored.overbored.net
Help, please! I'm trying to debug a standard C project, where I supplied
basically the same Makefiles as the auto-generated ones in a managed C
project. Everything seems to build fine. I then had to go into Project >
Properties > C/C++ Make Project > Binary Parser and check Cygwin PE
Parser and/or PE Windows Parser (I've tried either and both) in order to
start debugging.
Then, when I hit Debug, I can see from the Debug view's call stack that
execution arrives and stops at main() as expected, but then I can't do
anything, e.g.:
- clicking on the main() in the call stack doesn't take me to the source
location
- the cursor doesn't show up in the editor view
- stepping and breakpoints don't work
- etc.
I've tried using the Cygwin GDB Debugger (saw the above problem), GDB
Debugger (got "Failed to set up arguments, environment or working
directory"), and GDB Server (got "Error creating session: Target is not
responding (timed out)").
What am I missing? Please help! Thanks in advance.
|
|
|
| Re: Debugging standard C app via Cygwin [message #143798 is a reply to message #143792] |
Fri, 22 April 2005 09:50  |
| Eclipse User |
|
|
|
Originally posted by: overbored.overbored.net
I should mention that managed C projects work fine, but because I need
to work cross-platform (Eclipse for both Win and Linux), I need to use
standard C projects. I'm seeing my problem in Cygwin. I'm using Eclipse
3.1 and CDT 2.1.1.
overbored <overbored@overbored.net> wrote in
news:Xns964044A5C7FA1yangstaoverbored@206.191.52.34:
> Help, please! I'm trying to debug a standard C project, where I
supplied
> basically the same Makefiles as the auto-generated ones in a managed C
> project. Everything seems to build fine. I then had to go into Project
>
> Properties > C/C++ Make Project > Binary Parser and check Cygwin PE
> Parser and/or PE Windows Parser (I've tried either and both) in order
to
> start debugging.
>
> Then, when I hit Debug, I can see from the Debug view's call stack
that
> execution arrives and stops at main() as expected, but then I can't do
> anything, e.g.:
>
> - clicking on the main() in the call stack doesn't take me to the
source
> location
> - the cursor doesn't show up in the editor view
> - stepping and breakpoints don't work
> - etc.
>
> I've tried using the Cygwin GDB Debugger (saw the above problem), GDB
> Debugger (got "Failed to set up arguments, environment or working
> directory"), and GDB Server (got "Error creating session: Target is
not
> responding (timed out)").
>
> What am I missing? Please help! Thanks in advance.
>
|
|
|
| Re: Debugging standard C app via Cygwin [message #144138 is a reply to message #143798] |
Thu, 28 April 2005 02:33 |
| Eclipse User |
|
|
|
Originally posted by: stefan.uniblue.net
overbored wrote:
> I should mention that managed C projects work fine, but because I need
> to work cross-platform (Eclipse for both Win and Linux), I need to use
> standard C projects. I'm seeing my problem in Cygwin. I'm using Eclipse
> 3.1 and CDT 2.1.1.
I am not sure if I am getting this right but why do you say you require
standard make files over managed make files for cross-platform? When
choosing managed make files I can choose the output type (including
different OSes). I would assume as Cygwin and GCC are both cross platform
that the environment will produce the requested output. It will simply
appear as a second project pointo to the same source.
Does that make sense?
Stefan
|
|
|
Powered by
FUDForum. Page generated in 0.17083 seconds
Home