On 01/23/2013 01:35 PM, Christopher Faylor wrote:
On Wed, Jan 23, 2013 at 01:17:45PM -0500, Tom Honermann wrote:
I see you checked in a change to detect the infinite recursion. I'd
call that good enough.
That probably is relatively ok given that you're trying to terminate the
process anyway b
On Wed, Jan 23, 2013 at 01:17:45PM -0500, Tom Honermann wrote:
>On 01/23/2013 12:26 AM, Christopher Faylor wrote:
>> On Tue, Jan 22, 2013 at 10:20:20PM -0500, Tom Honermann wrote:
>>> However, just as I was about to give up testing, I hit one more new
>>> issue. One of the ctrl-c events sent bash
On 01/23/2013 12:26 AM, Christopher Faylor wrote:
On Tue, Jan 22, 2013 at 10:20:20PM -0500, Tom Honermann wrote:
However, just as I was about to give up testing, I hit one more new
issue. One of the ctrl-c events sent bash into what appeared to be an
infinite loop emitting error messages like t
On Tue, Jan 22, 2013 at 10:20:20PM -0500, Tom Honermann wrote:
>On 01/20/2013 05:08 PM, Tom Honermann wrote:
>> However, I was still able to reproduce another case. As before, one of
>> the processes is being left running when the rest are terminated. The
>> "abandoned" process appears to be in a
On 01/20/2013 05:08 PM, Tom Honermann wrote:
However, I was still able to reproduce another case. As before, one of
the processes is being left running when the rest are terminated. The
"abandoned" process appears to be in a live-lock state with two threads
(threads 1 and 2) running at 100%. O
On 01/19/2013 12:58 AM, Christopher Faylor wrote:
On Fri, Jan 18, 2013 at 03:11:03PM -0500, Tom Honermann wrote:
On 01/16/2013 05:23 PM, Christopher Faylor wrote:
On Wed, Jan 16, 2013 at 03:18:47PM -0500, Tom Honermann wrote:
I managed to duplicate a hang by changing your .bat file to use "slee
On Fri, Jan 18, 2013 at 03:11:03PM -0500, Tom Honermann wrote:
>On 01/16/2013 05:23 PM, Christopher Faylor wrote:
>> On Wed, Jan 16, 2013 at 03:18:47PM -0500, Tom Honermann wrote:
>> I managed to duplicate a hang by changing your .bat file to use "sleep
>> 2" rather than false. I'm investigating n
On 01/16/2013 05:23 PM, Christopher Faylor wrote:
On Wed, Jan 16, 2013 at 03:18:47PM -0500, Tom Honermann wrote:
I managed to duplicate a hang by changing your .bat file to use "sleep
2" rather than false. I'm investigating now.
I noticed that you checked in some additional changes on the 16th
On Wed, Jan 16, 2013 at 03:18:47PM -0500, Tom Honermann wrote:
>I previously mentioned that problems can be duplicated without mintty.
>Here are detailed steps for how to reproduce without mintty.
I was responding to your latest bug report which mentioned mintty.
I managed to duplicate a hang by
On 01/16/2013 02:14 PM, Christopher Faylor wrote:
Again, if I hit CTRL-C while running ./test.bat in mintty then test.bat
exits immediately, as expected. Hitting ctrl-c repeatedly after that
point gives me a new bash prompt.
Yes, that is what is expected to happen. What I am reporting is that
On 01/16/2013 01:59 PM, Christopher Faylor wrote:
On Wed, Jan 16, 2013 at 01:51:11PM -0500, Tom Honermann wrote:
Can you elaborate on what resources you are referring to? I fail to
see how the Cygwin binaries run via the .bat file could conflict with
mintty (or the top level bash process) since
On Wed, Jan 16, 2013 at 11:37:43AM -0500, Tom Honermann wrote:
>On 01/15/2013 09:04 PM, Christopher Faylor wrote:
>> On Tue, Jan 15, 2013 at 05:16:57PM -0500, Tom Honermann wrote:
>>> I noticed that some changes were checked in related to signal handling
>>> and process termination recently, so I d
On Wed, Jan 16, 2013 at 01:51:11PM -0500, Tom Honermann wrote:
>Can you elaborate on what resources you are referring to? I fail to
>see how the Cygwin binaries run via the .bat file could conflict with
>mintty (or the top level bash process) since the intervening cmd.exe
>execution would have blo
On 01/16/2013 01:05 PM, Earnie Boyd wrote:
On Wed, Jan 16, 2013 at 12:42 PM, Tom Honermann wrote:
On 01/16/2013 11:53 AM, marco atzeri wrote:
On 1/16/2013 5:37 PM, Tom Honermann wrote:
4) Launch mintty using an existing Cygwin installation. Naturally, this
will run a shell from the existi
On Wed, Jan 16, 2013 at 12:42 PM, Tom Honermann wrote:
> On 01/16/2013 11:53 AM, marco atzeri wrote:
>>
>> On 1/16/2013 5:37 PM, Tom Honermann wrote:
>>
>>>
>>> 4) Launch mintty using an existing Cygwin installation. Naturally, this
>>> will run a shell from the existing Cygwin install.
>>>
>>> 5
On 01/16/2013 11:53 AM, marco atzeri wrote:
On 1/16/2013 5:37 PM, Tom Honermann wrote:
4) Launch mintty using an existing Cygwin installation. Naturally, this
will run a shell from the existing Cygwin install.
5) Change directories to the usr/bin directory of the snapshot.
This will cause
On 1/16/2013 5:37 PM, Tom Honermann wrote:
4) Launch mintty using an existing Cygwin installation. Naturally, this
will run a shell from the existing Cygwin install.
5) Change directories to the usr/bin directory of the snapshot.
This will cause a cygwin1.dll collision between the two vers
On 01/15/2013 09:04 PM, Christopher Faylor wrote:
On Tue, Jan 15, 2013 at 05:16:57PM -0500, Tom Honermann wrote:
I noticed that some changes were checked in related to signal handling
and process termination recently, so I downloaded the most recent
snapshot (20130114) and tested again. I was s
On Tue, Jan 15, 2013 at 05:16:57PM -0500, Tom Honermann wrote:
>I noticed that some changes were checked in related to signal handling
>and process termination recently, so I downloaded the most recent
>snapshot (20130114) and tested again. I was still able to produce
>hanging processes (includ
On 01/02/2013 04:24 PM, Tom Honermann wrote:
On 01/02/2013 03:48 PM, Christopher Faylor wrote:
I managed to duplicate a hang by really stressing ctrl-c a loop. It
uncovers some rather amazing Windows behavior which I have to think
about. Apparently ExitThread can be called recursively within t
20 matches
Mail list logo
