Re: make signal text descriptions

2003-11-01 Thread J. Grant
Hi, #define SIGINT 2 /* Interactive attention */ #define SIGILL 4 /* Illegal instruction */ #define SIGFPE 8 /* Floating point error */ #define SIGSEGV 11 /* Segmentation violation */ #define SIGTERM 15 /* Termination request *

Re: make signal text descriptions

2003-10-30 Thread Earnie Boyd
J. Grant wrote: Hi Earnie, ok, I wonder if win32 has extra signals, this code 127, could these be supported for win32 ports? #define SIGINT 2 /* Interactive attention */ #define SIGILL 4 /* Illegal instruction */ #define SIGFPE 8 /* Floating point err

Re: make signal text descriptions

2003-10-29 Thread Eli Zaretskii
> Date: Thu, 30 Oct 2003 00:02:55 + > From: "J. Grant" <[EMAIL PROTECTED]> > > I noticed on this list list they talk about it being a failed exec: > > http://www.cygwin.com/ml/cygwin/2003-06/msg00674.html I doubt if this is a signal. It's more probably an error code from a library function

Re: make signal text descriptions

2003-10-29 Thread J. Grant
Hi Earnie, ok, I wonder if win32 has extra signals, this code 127, could these be supported for win32 ports? #define SIGINT 2 /* Interactive attention */ #define SIGILL 4 /* Illegal instruction */ #define SIGFPE 8 /* Floating point error */ #define SI

Re: make signal text descriptions

2003-10-29 Thread Earnie Boyd
J. Grant wrote: Hello, We use the system service to translate the code if the system provides it (many UNIX systems provide strsignal() for example). If not we have a predefined set of signals we translate, but if the signal is not a member of that predefined list it's not translated. ok, I won

Re: make signal text descriptions

2003-10-29 Thread J. Grant
Hello, What port of Make, specifically, do you use? Hello, I am using a native win32 build I created of 3.80. Kind regards JG ___ Bug-make mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-make

Re: make signal text descriptions

2003-10-29 Thread J. Grant
Hello, We use the system service to translate the code if the system provides it (many UNIX systems provide strsignal() for example). If not we have a predefined set of signals we translate, but if the signal is not a member of that predefined list it's not translated. ok, I wonder if win32 has e

Re: make signal text descriptions

2003-10-29 Thread Eli Zaretskii
> Date: Wed, 29 Oct 2003 21:07:39 + > From: "J. Grant" <[EMAIL PROTECTED]> > > ok, I've cc [EMAIL PROTECTED], so maybe someone can tell me if signal > numbers are decoded. Would you include this internally? or use a lib etc? The signal names are decoded if the underlying library supports th

Re: make signal text descriptions

2003-10-29 Thread Paul D. Smith
%% "J. Grant" <[EMAIL PROTECTED]> writes: jg> ok, I've cc [EMAIL PROTECTED], so maybe someone can tell me if jg> signal numbers are decoded. Would you include this internally? or jg> use a lib etc? We use the system service to translate the code if the system provides it (many UNIX systems

Re: make signal text descriptions

2003-10-29 Thread J. Grant
Hello, Thank you for your email. on the 29/10/03 00:03, Paul D. Smith wrote: %% "J. Grant" <[EMAIL PROTECTED]> writes: jg> Could the signals and errors that Make displays include the text jg> description of them? The same way that other programs do not jg> return the errno.h value, but th

Re: make signal text descriptions

2003-10-28 Thread Paul D. Smith
%% "J. Grant" <[EMAIL PROTECTED]> writes: jg> Could the signals and errors that Make displays include the text jg> description of them? The same way that other programs do not jg> return the errno.h value, but the text that it corresponds too. jg> e.g.: jg> Signal 127 GNU make does p

make signal text descriptions

2003-10-28 Thread J. Grant
Hello, Could the signals and errors that Make displays include the text description of them? The same way that other programs do not return the errno.h value, but the text that it corresponds too. Let me know if you would like to implement this for make. Kind regards JG e.g.: Signal 127 z:\b