This is the mail archive of the mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: gdb attach/detach kills the target process

On Wed, Jun 18, 2003 at 07:33:38PM -0400, Igor Pechtchanski wrote:
> On 18 Jun 2003, Sam Steingold wrote:
> > run a process in a cygwin window, find out its PID, run gdb in another
> > window, attach to that process, then detach from it.
> > the target process stops responding as soon as it is attached to.
> > detaching changes nothing.
> > only after I exit gdb, I get the original window responding, with the
> > terminal in raw start (need to do "reset" in bash) and the process that
> > gdb attached to dead.
> >
> > I tested this on python and clisp.
> That's the way Windows debugging works -- once you attach to a process,
> detaching from it kills the process.  No way around it.

...up to Windows 2000.  Since XP, Windows has a new function call to
detach from a process and let it running.  gdb is using this call if
it's availbale on the system.


Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Developer                      
Red Hat, Inc.

Unsubscribe info:
Problem reports:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]