[ptxdist] kill missing RT signals

[ptxdist] kill missing RT signals

[Jon Ringle]

I'm not sure if this is an issue with ptxdist or OSELAS toolchain or
something else, but I want to be able to send to systemd a SIGRTMIN+21
signal and I found that kill command does not report the RT signals:

$ kill -l
 1) SIGHUP       2) SIGINT       3) SIGQUIT      4) SIGILL
 5) SIGTRAP      6) SIGABRT      7) SIGBUS       8) SIGFPE
 9) SIGKILL     10) SIGUSR1     11) SIGSEGV     12) SIGUSR2
13) SIGPIPE     14) SIGALRM     15) SIGTERM     16) SIGSTKFLT
17) SIGCHLD     18) SIGCONT     19) SIGSTOP     20) SIGTSTP
21) SIGTTIN     22) SIGTTOU     23) SIGURG      24) SIGXCPU
25) SIGXFSZ     26) SIGVTALRM   27) SIGPROF     28) SIGWINCH
29) SIGIO       30) SIGPWR      31) SIGSYS

I thought may be it was the busybox kill, so I build the coreutils
kill, but it gives exactly the same output. I don't understand why
kill is not listing the RT signalse from SIGRTMIN to SIGRTMAX.

$ arm-v5te-linux-gnueabi-gcc --version
arm-v5te-linux-gnueabi-gcc (OSELAS.Toolchain-2013.12.1) 4.8.2
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

Target board has Linux-3.12

Anyone have any ideas?

Thanks,
Jon

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] kill missing RT signals

[Jon Ringle]

On Thu, Apr 10, 2014 at 8:58 PM, Jon Ringle <jon@ringle.org> wrote:
> I'm not sure if this is an issue with ptxdist or OSELAS toolchain or
> something else, but I want to be able to send to systemd a SIGRTMIN+21
> signal and I found that kill command does not report the RT signals:
>
> $ kill -l
>  1) SIGHUP       2) SIGINT       3) SIGQUIT      4) SIGILL
>  5) SIGTRAP      6) SIGABRT      7) SIGBUS       8) SIGFPE
>  9) SIGKILL     10) SIGUSR1     11) SIGSEGV     12) SIGUSR2
> 13) SIGPIPE     14) SIGALRM     15) SIGTERM     16) SIGSTKFLT
> 17) SIGCHLD     18) SIGCONT     19) SIGSTOP     20) SIGTSTP
> 21) SIGTTIN     22) SIGTTOU     23) SIGURG      24) SIGXCPU
> 25) SIGXFSZ     26) SIGVTALRM   27) SIGPROF     28) SIGWINCH
> 29) SIGIO       30) SIGPWR      31) SIGSYS
>
> I thought may be it was the busybox kill, so I build the coreutils
> kill, but it gives exactly the same output. I don't understand why
> kill is not listing the RT signalse from SIGRTMIN to SIGRTMAX.
>
> $ arm-v5te-linux-gnueabi-gcc --version
> arm-v5te-linux-gnueabi-gcc (OSELAS.Toolchain-2013.12.1) 4.8.2
> Copyright (C) 2013 Free Software Foundation, Inc.
> This is free software; see the source for copying conditions.  There is NO
> warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
>
> Target board has Linux-3.12
>
> Anyone have any ideas?

Ok... I've a little confused about this. It seems like I have 2
different versions of kill installed on my target, but I can't figure
out where the 1st one is located:

root@ec1k:/# kill -l
 1) SIGHUP       2) SIGINT       3) SIGQUIT      4) SIGILL
 5) SIGTRAP      6) SIGABRT      7) SIGBUS       8) SIGFPE
 9) SIGKILL     10) SIGUSR1     11) SIGSEGV     12) SIGUSR2
13) SIGPIPE     14) SIGALRM     15) SIGTERM     16) SIGSTKFLT
17) SIGCHLD     18) SIGCONT     19) SIGSTOP     20) SIGTSTP
21) SIGTTIN     22) SIGTTOU     23) SIGURG      24) SIGXCPU
25) SIGXFSZ     26) SIGVTALRM   27) SIGPROF     28) SIGWINCH
29) SIGIO       30) SIGPWR      31) SIGSYS
root@ec1k:/# which kill
/bin/kill
root@ec1k:/# /bin/kill -l
 1) HUP
 2) INT
 3) QUIT
 4) ILL
 5) TRAP
 6) ABRT
 7) BUS
 8) FPE
 9) KILL
10) USR1
11) SEGV
12) USR2
13) PIPE
14) ALRM
15) TERM
16) STKFLT
17) CHLD
18) CONT
19) STOP
20) TSTP
21) TTIN
22) TTOU
23) URG
24) XCPU
25) XFSZ
26) VTALRM
27) PROF
28) WINCH
29) POLL
30) PWR
31) SYS
32) RTMIN
64) RTMAX

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] kill missing RT signals

[Jon Ringle]

On Fri, Apr 11, 2014 at 11:34 AM, Jon Ringle <jon@ringle.org> wrote:
> Ok... I've a little confused about this. It seems like I have 2
> different versions of kill installed on my target, but I can't figure
> out where the 1st one is located:
>
> root@ec1k:/# kill -l
>  1) SIGHUP       2) SIGINT       3) SIGQUIT      4) SIGILL
>  5) SIGTRAP      6) SIGABRT      7) SIGBUS       8) SIGFPE
>  9) SIGKILL     10) SIGUSR1     11) SIGSEGV     12) SIGUSR2
> 13) SIGPIPE     14) SIGALRM     15) SIGTERM     16) SIGSTKFLT
> 17) SIGCHLD     18) SIGCONT     19) SIGSTOP     20) SIGTSTP
> 21) SIGTTIN     22) SIGTTOU     23) SIGURG      24) SIGXCPU
> 25) SIGXFSZ     26) SIGVTALRM   27) SIGPROF     28) SIGWINCH
> 29) SIGIO       30) SIGPWR      31) SIGSYS
> root@ec1k:/# which kill
> /bin/kill
> root@ec1k:/# /bin/kill -l
>  1) HUP
>  2) INT
>  3) QUIT
>  4) ILL
>  5) TRAP
>  6) ABRT
>  7) BUS
>  8) FPE
>  9) KILL
> 10) USR1
> 11) SEGV
> 12) USR2
> 13) PIPE
> 14) ALRM
> 15) TERM
> 16) STKFLT
> 17) CHLD
> 18) CONT
> 19) STOP
> 20) TSTP
> 21) TTIN
> 22) TTOU
> 23) URG
> 24) XCPU
> 25) XFSZ
> 26) VTALRM
> 27) PROF
> 28) WINCH
> 29) POLL
> 30) PWR
> 31) SYS
> 32) RTMIN
> 64) RTMAX

I didn't realize until now that bash has a builtin kill command, which
is what it seems that is what was running on my 1st 'kill -l'
invocation above.

Jon

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] kill missing RT signals

[Robert Schwebel]

On Fri, Apr 11, 2014 at 12:01:14PM -0400, Jon Ringle wrote:
> I didn't realize until now that bash has a builtin kill command, which
> is what it seems that is what was running on my 1st 'kill -l'
> invocation above.

You can find out what's really used with type:

rsc@callisto:~$ type kill
kill is a shell builtin

rsc
-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

Re: [ptxdist] kill missing RT signals

[Michael Olbrich]

On Fri, Apr 11, 2014 at 12:01:14PM -0400, Jon Ringle wrote:
> On Fri, Apr 11, 2014 at 11:34 AM, Jon Ringle <jon@ringle.org> wrote:
> > Ok... I've a little confused about this. It seems like I have 2
> > different versions of kill installed on my target, but I can't figure
> > out where the 1st one is located:
[...]
> I didn't realize until now that bash has a builtin kill command, which
> is what it seems that is what was running on my 1st 'kill -l'
> invocation above.

As you noticed, it's a bash builtin, and there is a autoconf AC_TRY_RUN
check for it in the bash configure script that fails because we're
cross-compiling I think adding bash_cv_unusable_rtsigs=yes to BASH_ENV
might help...

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de