[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, 30 Jul 2005 19:50:29 +0300

> Date: Sat, 30 Jul 2005 15:31:43 +0100
> From: "J. Grant" <address@hidden>
> 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

Since I couldn't reproduce the original problem, I looked into the
sources.  It looks like this _should_ work in the Windows build:
config.h.W32 says that all the facilities for printing signal names
are unavailable, and then signame.c sets up a table of signal names
according to the value of NSIG and the SIG* symbols defined by the
signal.h header.  So if Make receives a real signal, one of those that
can happen on Windows, it should print a correct description.

127 is not a valid signal code on Windows.

Thus, without a test case, I don't see how this can be debugged and

reply via email to

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