On 2007-02-19, Chris Balthrop <[email protected]> wrote:
> I am now trying to use the eclipse setup and I have a "continue" problem
> simular? to the problem Grant mentioned 20061113. The GCC compile works
> fine, and the program loads and starts ok. I can single step and set
> breaks and run to them. However, when I "continue" without a
> breakpoint, I cannot regain control back to the debugger screen.
>
> Grant mentioned using "setsid" but I am unfamilar with this command in
> CYGWIN. Can anyone give me some hints on how this might work on my
> win2000/cygwin setup?
I'm afraid I don't know what to do about it on Win2K/cygwin,
but I can explain exactly what the problem was...
What was happening to me was that I was starting the gdb-proxy
from gdb. When I hit ctrl-C, SIGINT was being sent to both gdb
and gdb-proxy. GDB handles SIGINT and interprets it as a
request from the user to stop the target. gdb-proxy doesn't
handle SIGINT, so it gets aborted.
What the setsid command did was run gdb-proxy in a different
process group (not sure that's the right phrase), so that when
I hit Ctrl-C SIGINT was sent only to gdb and not to gdb-proxy.
I don't know if that's what's happening to you or not. After
you've hit Ctrl-C, is the gdb-proxy process gone?
--
Grant Edwards grante Yow! Jesus is my
at POSTMASTER GENERAL...
visi.com
