Mail Archives: djgpp/1998/11/12/16:14:32
MrWiggley wrote :
>
> Everything comples and runs fine, but try placing a breakpoint on the printf
> line, running the program, then opening the dissasembler. Press F8 to get to
> the "call AddFour" instruction, then press F7. This will bring you to the
> disasembly of the AddFour funciton. Press F8, and the program crashes.
> However, if you move the cursor down to say, "mov eax, [ebp + x_AddFour", and
> press F4, everything works fine!
This seems to be a bug in gdb (the core of RHIDE's debugger). To check
it, please compile the following file t.c
/* start of t.c */
int t1()
{
return 0;
}
int main()
{
return t1();
}
/* end of t.c */
with
gcc -o t.exe -g t.c
and then run gdb on it typing the following comands:
gdb t.exe
b main
r
si
ni
As you can see, gdb cannot handle correct the 'next instruction'
command, when the current execution point is inside the stackframe
for the current function it is creating.
Robert
--
******************************************************
* email: Robert Hoehne <robert DOT hoehne AT gmx DOT net> *
* Post: Am Berg 3, D-09573 Dittmannsdorf, Germany *
* WWW: http://www.tu-chemnitz.de/~sho/rho *
******************************************************
- Raw text -