Mail Archives: cygwin/2004/02/16/11:40:22
On Feb 16 17:13, Corinna Vinschen wrote:
> On Feb 16 10:03, David Fritz wrote:
> > Corinna Vinschen wrote:
> > >On Feb 15 15:11, linda w wrote:
> > >
> > >>I decided to trace a 3 day long running process (the dd/bzip program)
> > >>that was
> > >>nearing completion (had a couple hundred meg to go), and much to my
> > >>chagrin,
> > >>when I wanted to stop tracing, I pressed control-c -- and unlike the
> > >>behavior I'm
> > >>used to in linux, it didn't just terminate the process being traced, but
> > >>also
> > >>terminated the program that had been attached to!
> > >>
> > >>Very very much of a bummer, since it takes 3+ days, apparently, to run
> > >>and come near
> > >>to completing this test. Very, very sad....oh well...
> > >>
> > >>Is this a "feature" or a "bug"?
> > >
> > >It's Windows.
> >
> > Indeed it is. Though I'd note that Windows XP and later allow debuggers to
> > detach from a process without killing it. (DebugActiveProcessStop(),
> > DebugSetProcessKillOnExit()).
>
> Indeed, it's already implemented in GDB.
Btw., you already can have a similar behaviour with strace. At least
on XP, I didn't check on earlier versions.
If you start the process in one window and attach with strace from
another window, then, when you break strace, it won't stop the child.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin AT cygwin DOT com
Red Hat, Inc.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -