octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #39089] Incomplete list of OS signals in the b


From: Dan Sebald
Subject: [Octave-bug-tracker] [bug #39089] Incomplete list of OS signals in the builtin SIG function
Date: Thu, 30 May 2013 20:11:24 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:18.0) Gecko/20100101 Firefox/18.0 SeaMonkey/2.15

Follow-up Comment #3, bug #39089 (project octave):

Ha, there looks to be a bug in the list software when underscore follows
"verbatim" delimiter.  Here's the original message removing the "verbatim"
delimiter to see if the whole thing goes through this time:

Thank you...  This gnulib siglist.h/siglist.c looks like it might be a good
idea.  I'm guessing that signals.h (bits/signum.h) is constructed as part of
the kernel compilation process (or maybe it is library level). 
siglist.h/siglist.c is meant to reflect that.  Here's a siglist.c from far
back

http://www.opensource.apple.com/source/bash/bash-30/bash/siglist.c

that is similar to Octave's.  Octave's siglist.h has a comment referencing
Emacs.  So perhaps Octave signal interpretation predate's gnulib's code.

The gnulib github has a recent copyright suggesting it is fairly well
maintained.  There's a gnulib file strsignal.c that seems to be the equivalent
of Octave's siglist.c but gets the description from somewhere that isn't
obvious (INTUSE ?) and I'm not sure why it is adding an underscore
_sys_siglist which is typically done when referencing C variables inside
assembly language code.

The siglist.h in gnulib doesn't have the following from Octave's siglist.h:


      sys_siglist[SIGAIO] = "LAN I/O interrupt";
      sys_siglist[SIGCLD] = "Child status changed";
      sys_siglist[SIGDANGER] = "Swap space dangerously low";
      sys_siglist[SIGDGNOTIFY] = "Notification message in queue";
      sys_siglist[SIGFREEZE] = "SIGFREEZE";
      sys_siglist[SIGGRANT] = "Monitor mode granted";
      sys_siglist[SIGLWP] = "SIGLWP";
      sys_siglist[SIGMSG] = "Monitor mode data available";
      sys_siglist[SIGPHONE] = "SIGPHONE";
      sys_siglist[SIGPOLL] = "Pollable event occurred";
      sys_siglist[SIGPTY] = "PTY I/O interrupt";
      sys_siglist[SIGRETRACT] = "Need to relinguish monitor mode";
      sys_siglist[SIGSAK] = "Secure attention";
      sys_siglist[SIGSOUND] = "Sound completed";
      sys_siglist[SIGSTP] = "Stopped (user)";
      sys_siglist[SIGTHAW] = "SIGTHAW";
      sys_siglist[SIGWAITING] = "Process's LWPs are blocked";
      sys_siglist[SIGWIND] = "SIGWIND";


The only two of these that are defined on my system are SIGCLD (#17 which is
the same as SIGCHLD) and SIGPOLL (#29 which is the same as SIGIO).  So my
system should be covered by gnulib's siglist.h.

There is also a sig2str.c in gnulib which does contain all the definitions
including those I listed above, along with a short comment categorizing them
as


    /* GNU/Linux 2.2 and Solaris 8.  */


There are a half dozen other groups of extensions as well.  So the signal
interpretation does seem to be covered fairly well in gnulib.


    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?39089>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

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