| GDB Eclipse Issues [message #183063] |
Thu, 25 January 2007 19:13  |
Eclipse User |
|
|
|
Originally posted by: jkalinowski.microwavedata.com
Hey all,
Not sure if this is right section to file this under but ... is there
any known issues with GDB and Eclipse? Like output wise, messages saying
"Previous frame inner to this frame (corrupt stack?)". Could this be
just an issue with GDB or is it a true problem with the program. I know
that GDB already has issues with stack traces and that they aren't
always done correctly. Thanks for the help.
Jeremy
|
|
|
| Re: GDB Eclipse Issues [message #183072 is a reply to message #183063] |
Fri, 26 January 2007 11:32  |
| Eclipse User |
|
|
|
Originally posted by: ed_06.tantec.de
Jerermy schrieb:
> Not sure if this is right section to file this under but ... is there
> any known issues with GDB and Eclipse? Like output wise, messages saying
> "Previous frame inner to this frame (corrupt stack?)". Could this be
> just an issue with GDB or is it a true problem with the program. I know
> that GDB already has issues with stack traces and that they aren't
> always done correctly. Thanks for the help.
I'm using MinGW for windows and I had a problem like this, when trying
to update from gcc 3.3.1 to a gcc 4.x version. It seemed to be
successful, but when starting the debugger, it always told me about
"Previous frame...". First I thought, there is an existing problem shown
by the update and searched a lot, but finally I was sure, there was no
problem with program, only with debugger - it always tells about this
problem, also caused by simple test programs, where definitely was no
possibility for "corrupt stack".
I tried other versions of GDB (at all I was busy with this item for two
long days!), but finally I capitulated and stepped back to 3.3.1 version.
|
|
|
Powered by
FUDForum. Page generated in 0.02170 seconds
] 
Search
Help
Register
Login
Home
