gdb question

[Saveliy Tretiakov]

Hi. I'm trying to debug ros with gdb (according to GvG's tutorial) and I 
have a problem. After I attach gdb, reactos boots into desktop and then 
freezes with endless sigservs. Mouse cursor is not moving. Any ideas?

(gdb) target remote localhost:567
Remote debugging using localhost:567
0x800a8297 in ?? ()
 
(gdb) continue
Continuing.
 
*** Now ros boots into desktop. ***

Program received signal SIGSEGV, Segmentation fault.
0x0040aa12 in ?? ()
 
(gdb) continue
Continuing.
Can't send signals to this remote system.  SIGSEGV not sent.
 
Program received signal SIGSEGV, Segmentation fault.
0x0040aa12 in ?? ()
 
(gdb) continue
Continuing.
Can't send signals to this remote system.  SIGSEGV not sent.
 
Program received signal SIGSEGV, Segmentation fault.
0x0040aa12 in ?? ()

......

[Ge van Geldorp]

>   From: Saveliy Tretiakov
>  
>  Hi. I'm trying to debug ros with gdb (according to GvG's
>  tutorial) and I have a problem. After I attach gdb, reactos boots into 
>  desktop and then freezes with endless sigservs.
>  Mouse cursor is not moving. Any ideas? 
The endless loop is "normal" behaviour. When a fault occurs, the processor
state is saved with EIP pointing to the faulting instruction. The gdb stub
takes control. When you "c"ontinue, the processor state is restored and the
faulting instruction is re-executed. Since the processor state is the same
as the first time, this will generate a new fault, launching you into gdb
again.

I don't know why it encounters a fault in the first place. You can look at
the thread view and then find the "Running" thread, this should show you the
process in which the fault occurs.

GvG