[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: Earnie Boyd
Subject: Re: WINDOWS32 "Signal 127" due to a path in quotes bug
Date: Mon, 1 Aug 2005 11:42:47 +0000

On 2:31:43 pm 2005-07-30 "J. Grant" <address@hidden> wrote:
> Hello,
> Previously we have discussed this:
> "Re: make signal text descriptions"
> There are two cases where I think we should display a more accurate
> error code Error description:
> "Signal 127" (quoted paths) (Also "Error 127", if this is the same)
> and "Error 255"  (binary did not exist)
> It is clearly a failed exec
> (, and as Earnie
> pointed out this is not a signal, but a return code.  For these
> reasons I think we should display an appropriate message, at least on
> WINDOWS32 builds
> I could not replicate the "Signal 127" message, I could replicate
> "Error 127", maybe the different win32 build options effect this in a
> way that it is incorrectly named as a "Signal" 127 error.
> I attatch a test case which replicates "Error 127", what I wonder is
> why CreateProcess() is used to swpawn in the first case, and /bin/sh
> is used in the 2nd case?
> makefile_Error_127.test
> Does anyone know where 127 and 255 values are documented as indicating
> something in partciular?

$ grep 127 /include/winerror.h

$ grep 255 /include/winerror.h


reply via email to

[Prev in Thread] Current Thread [Next in Thread]