[haiku-bugs] Re: [Haiku] #9046: kill -l command shows incorrect list of signals

  • From: "Prasad" <trac@xxxxxxxxxxxx>
  • Date: Sat, 06 Oct 2012 17:14:05 -0000

#9046: kill -l command shows incorrect list of signals
-----------------------------------------------+---------------------------
   Reporter:  Prasad                           |      Owner:  nobody
       Type:  bug                              |     Status:  new
   Priority:  normal                           |  Milestone:  R1
  Component:  Applications/Command Line Tools  |    Version:
 Resolution:                                   |  R1/Development
 Blocked By:                                   |   Keywords:  kill, signal
Has a Patch:  0                                |   Blocking:
                                               |   Platform:  All
-----------------------------------------------+---------------------------

Comment (by Prasad):

 As I understand the mapping from signal number to string kept in the file

 {{{
 src/bin/bash/signames_haiku.h
 }}}

 The comment in the file suggest that the file is auto-generated using a
 tool mksignames.

 Running the tool shows the following output
 {{{
 prasad@pjoshi:~/sources/Haiku/haiku$
 ./generated/objects/linux/x86_64/release/bin/bash/mksignames
 /* This file was automatically created by
 ./generated/objects/linux/x86_64/release/bin/bash/mksignames.
    Do not edit.  Edit support/signames.c instead. */

 /* A translation list so we can be polite to our users. */
 char *signal_names[NSIG + 4] = {
     "EXIT",
     "SIGHUP",
     "SIGINT",
     "SIGQUIT",
     "SIGILL",
     "SIGTRAP",
     "SIGABRT",
     "SIGBUS",
     "SIGFPE",
     "SIGKILL",
     "SIGUSR1",
     "SIGSEGV",
     "SIGUSR2",
     "SIGPIPE",
     "SIGALRM",
     "SIGTERM",
     "SIGSTKFLT",
     "SIGCHLD",
     "SIGCONT",
     "SIGSTOP",
     "SIGTSTP",
     "SIGTTIN",
     "SIGTTOU",
     "SIGURG",
     "SIGXCPU",
     "SIGXFSZ",
     "SIGVTALRM",
     "SIGPROF",
     "SIGWINCH",
     "SIGIO",
     "SIGPWR",
     "SIGSYS",
     "SIGJUNK(32)",
     "SIGJUNK(33)",
     "SIGRTMIN",
     "SIGRTMIN+1",
     "SIGRTMIN+2",
     "SIGRTMIN+3",
     "SIGRTMIN+4",
     "SIGRTMIN+5",
     "SIGRTMIN+6",
     "SIGRTMIN+7",
     "SIGRTMIN+8",
     "SIGRTMIN+9",
     "SIGRTMIN+10",
     "SIGRTMIN+11",
     "SIGRTMIN+12",
     "SIGRTMIN+13",
     "SIGRTMIN+14",
     "SIGRTMIN+15",
     "SIGRTMAX-14",
     "SIGRTMAX-13",
     "SIGRTMAX-12",
     "SIGRTMAX-11",
     "SIGRTMAX-10",
     "SIGRTMAX-9",
     "SIGRTMAX-8",
     "SIGRTMAX-7",
     "SIGRTMAX-6",
     "SIGRTMAX-5",
     "SIGRTMAX-4",
     "SIGRTMAX-3",
     "SIGRTMAX-2",
     "SIGRTMAX-1",
     "SIGRTMAX",
     "DEBUG",
     "ERR",
     "RETURN",
     (char *)0x0
 };

 #define initialize_signames()
 }}}


 This seems to be exact list reported on a Linux system, I mean, the signal
 name and position matches with Linux machine.


 AFAIK, this auto-generated list cannot be used, since Haiku uses few
 propitiatory signals like  'SIGKILLTHR' for example.


 So the question I have is, How was the signames_haiku.h generated
 initially? was it auto-generated?
 If it was not auto-generated, would it be okay if I manually edit the file
 and add SIGBUS at 30'th location?

-- 
Ticket URL: <http://dev.haiku-os.org/ticket/9046#comment:1>
Haiku <http://dev.haiku-os.org>
Haiku - the operating system.

Other related posts: