[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: WINDOWS32 "Signal 127" due to a path in quotes bug
From: |
Eli Zaretskii |
Subject: |
Re: WINDOWS32 "Signal 127" due to a path in quotes bug |
Date: |
Sat, 06 Aug 2005 17:33:42 +0300 |
> Date: Mon, 1 Aug 2005 22:37:57 -0400
> Cc: Eli Zaretskii <address@hidden>, address@hidden
> From: "Paul D. Smith" <address@hidden>
>
> I was assuming they don't terminate because the operating system
> (Windows) is sending the SIGINT to only the "main" program (in this case
> make), and not sending it to all the processes that make invokes. In
> other words, Windows doesn't have the concept of a process group or, at
> least, it doesn't work the same way.
In fact, Windows behaves exactly like Posix platforms in this case.
> On a POSIX system, every signal has a default behavior: either the
> signal is ignored or the process is killed. If you don't define your
> own handler for the signal, then the default behavior is invoked.
The same happens on Windows.
- Re: WINDOWS32 "Signal 127" due to a path in quotes bug, (continued)
- Re: WINDOWS32 "Signal 127" due to a path in quotes bug, Paul D. Smith, 2005/08/01
- Re: WINDOWS32 "Signal 127" due to a path in quotes bug, J. Grant, 2005/08/01
- Re: WINDOWS32 "Signal 127" due to a path in quotes bug, J. Grant, 2005/08/03
- Re: WINDOWS32 "Signal 127" due to a path in quotes bug, Eli Zaretskii, 2005/08/04
- Re: WINDOWS32 "Signal 127" due to a path in quotes bug, Eli Zaretskii, 2005/08/06
- Re: WINDOWS32 "Signal 127" due to a path in quotes bug, Paul D. Smith, 2005/08/06
- Re: WINDOWS32 "Signal 127" due to a path in quotes bug,
Eli Zaretskii <=
Re: WINDOWS32 "Signal 127" due to a path in quotes bug, Eli Zaretskii, 2005/08/06
Re: WINDOWS32 "Signal 127" due to a path in quotes bug, Alessandro Vesely, 2005/08/07