[Patch]: Setting the winpid in pinfo

2004-09-07 Thread Pierre A. Humblet
I am looking at some oddities involving ^C and signals. In the current code, set_myself sets the dwProcessId when a pinfo is created. The upshot is that signals to a process that is exec'ing will be prematurely directed to the child (using a meaningless handle from the parent). The bug can be fix

Re: [Patch]: Setting the winpid in pinfo

2004-09-07 Thread Christopher Faylor
On Tue, Sep 07, 2004 at 09:26:02PM -0400, Pierre A. Humblet wrote: >I am looking at some oddities involving ^C and signals. > >In the current code, set_myself sets the dwProcessId when a pinfo is >created. The upshot is that signals to a process that is exec'ing will >be prematurely directed to th

Re: [Patch]: Setting the winpid in pinfo

2004-09-10 Thread Pierre A. Humblet
At 12:15 AM 9/8/2004 -0400, Christopher Faylor wrote: >On Tue, Sep 07, 2004 at 09:26:02PM -0400, Pierre A. Humblet wrote: >>Also, on WinME, simply holding down ^C in the bash shell will >>cause a crash (thanks to Errol Smith) >>~> 142 [sig] BASH 1853149 handle_threadlist_exception: >>handle_t

Re: [Patch]: Setting the winpid in pinfo

2004-09-10 Thread Christopher Faylor
On Fri, Sep 10, 2004 at 09:29:35PM -0400, Pierre A. Humblet wrote: >At 12:15 AM 9/8/2004 -0400, Christopher Faylor wrote: >>On Tue, Sep 07, 2004 at 09:26:02PM -0400, Pierre A. Humblet wrote: > >>>Also, on WinME, simply holding down ^C in the bash shell will >>>cause a crash (thanks to Errol Smith)

Re: [Patch]: Setting the winpid in pinfo

2004-09-10 Thread Pierre A. Humblet
At 10:49 PM 9/10/2004 -0400, Christopher Faylor wrote: >On Fri, Sep 10, 2004 at 09:29:35PM -0400, Pierre A. Humblet wrote: >>Here are 2 other small changes. >> >>When killing the (system stressing) program I used to track the >>fork bug, I noticed that it occasionally leaves stray processes >>behi

Re: [Patch]: Setting the winpid in pinfo

2004-09-10 Thread Christopher Faylor
On Fri, Sep 10, 2004 at 11:13:37PM -0400, Pierre A. Humblet wrote: >>If the child process has not become fully awake yet it should just exit now. > >Not if it is destined to ignore ^C. The group leader will wait until the >[grand]child has grown up and its sendsig is != NULL, and then send the >si

Re: [Patch]: Setting the winpid in pinfo

2004-09-10 Thread Pierre A. Humblet
At 12:11 AM 9/11/2004 -0400, Christopher Faylor wrote: >On Fri, Sep 10, 2004 at 11:13:37PM -0400, Pierre A. Humblet wrote: >>>If the child process has not become fully awake yet it should just exit now. >> >>Not if it is destined to ignore ^C. The group leader will wait until the >>[grand]child ha

Re: [Patch]: Setting the winpid in pinfo

2004-09-10 Thread Christopher Faylor
On Sat, Sep 11, 2004 at 12:29:26AM -0400, Pierre A. Humblet wrote: >In fact the way signals are delivered is current asymmetric: >- Default actions are handled by the sigthread asynchronously of the >mainthread. I don't know what this means. >- Signals that require a handler have to wait until th

Re: [Patch]: Setting the winpid in pinfo

2004-09-10 Thread Christopher Faylor
On Sat, Sep 11, 2004 at 12:29:26AM -0400, Pierre A. Humblet wrote: >For example, that would also prevent a process from being killed while >exec'ing, while the baby is still suspended. Of course an exec stub >should still handle the signal, somehow, although you expressed other >ideas earlier in t

Re: [Patch]: Setting the winpid in pinfo

2004-09-11 Thread Christopher Faylor
On Fri, Sep 10, 2004 at 09:29:35PM -0400, Pierre A. Humblet wrote: > * exceptions.cc: Add header files. > (ctrl_c_handler): Do nothing while a Cygwin subprocess is > starting. I checked in a variation of this patch which used myself->ppid_handle as a method for finding if the pro