Comment 16 for bug 492810

When I use gdb following this procedure:

Start gdb:
gdb 2>&1 | tee gdb-<program>.txt
(gdb) handle SIG33 pass nostop noprint
(gdb) set pagination 0
(gdb) attach <PID>
(If the program is running as root, use sudo gdb instead of just gdb above.)
Continue the <program>:
(gdb) continue
The program will continue running. Perform any actions necessary to reproduce the crash. If the program hangs but doesn't crash you can press ctrl+c in gdb while the program is frozen and then continue with the next step.

When I give the command continue, in the system monitor nautilus is "stopped" (that's what's written in the cpu % value),
and if I go back to gdb pressing cntrl+c to start the debug it gives me:
this sign:
^C
and does not responds to any of my commands...

Help would be appreciated