Debugging problem [message #84807] |
Wed, 29 October 2003 19:45 |
Eclipse User |
|
|
|
Originally posted by: user.domain.invalid
I am getting the following error message when running GDB on some C code:
Thread[1] (Suspended) <Stack is not available: Cannot access memory at
address 0x28>
This happens at a breakpoint. I cannot examine the values of any
variables at this point. The application will continue on past any
breakpoints and will terminate properly. I get this same message (but
with the address sometimes varying) at ALL breakpoints. I am using
minGW for compile and GDB for debugging. Any idea what is causing this?
This is CDT version 1.2, mingw version 3.2.3 and gdb 5.2.1 configured as
"i686-pc-mingw32". Is this really using my already installed gdb or is
eclipse using its own gdb installation?
Using (virtually) the same makefile in Dev-CPP debugs properly in Dev-CPP.
Bill Plyler
|
|
|
Re: Debugging problem [message #84824 is a reply to message #84807] |
Wed, 29 October 2003 21:45 |
Eclipse User |
|
|
|
Originally posted by: mikhailk.qnx.com
CDT uses the same gdb that is set in the "GDB debugger" field of the launch
configuration. This message is obviously the gdb reaction to the "backtrace"
command.
<user@domain.invalid> wrote in message news:bnp5bh$523$1@eclipse.org...
> I am getting the following error message when running GDB on some C code:
>
> Thread[1] (Suspended) <Stack is not available: Cannot access memory at
> address 0x28>
>
> This happens at a breakpoint. I cannot examine the values of any
> variables at this point. The application will continue on past any
> breakpoints and will terminate properly. I get this same message (but
> with the address sometimes varying) at ALL breakpoints. I am using
> minGW for compile and GDB for debugging. Any idea what is causing this?
>
> This is CDT version 1.2, mingw version 3.2.3 and gdb 5.2.1 configured as
> "i686-pc-mingw32". Is this really using my already installed gdb or is
> eclipse using its own gdb installation?
>
> Using (virtually) the same makefile in Dev-CPP debugs properly in Dev-CPP.
>
> Bill Plyler
>
|
|
|
Powered by
FUDForum. Page generated in 0.03465 seconds