touch-packages team mailing list archive

[John Samuel <1433155@xxxxxxxxxxxxxxxxxx>]

On executing the following command

$ grep SIGRTMIN /usr/include/ -r
/usr/include/asm-generic/signal.h:#define SIGRTMIN	32
/usr/include/x86_64-linux-gnu/asm/signal.h:#define SIGRTMIN	32
/usr/include/x86_64-linux-gnu/bits/signum.h:#define SIGRTMIN        (__libc_current_sigrtmin ())
/usr/include/x86_64-linux-gnu/bits/signum.h:#define __SIGRTMIN	32

and checking the source code of glibc-2.19/signal/allocrtsig.c
...
/* Return number of available real-time signal with highest priority.  */
int
__libc_current_sigrtmin (void)
{
#ifdef __SIGRTMIN
  if (!initialized)
    init ();
#endif
  return current_rtmin;
}
...

It seems that bash uses the value of current_rtmin

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bash in Ubuntu.
https://bugs.launchpad.net/bugs/1433155

Title:
  bash "kill -l" builtin gives wrong numbers for SIGRTMIN+n signals

Status in bash package in Ubuntu:
  New

Bug description:
  The command "grep SIGRTMIN /usr/include/ -r" gives me

  /usr/include/asm/signal.h:#define SIGRTMIN      32

  and a bunch of other defines with the same value. But if I ask bash's
  "kill" builtin via "kill -l", I get "34) SIGRTMIN". What's
  interesting, there's actually no number 32 listed at all. Number 34
  goes right after 31, where the right 32 should appear. The other names
  defined via SIGRTMIN are also wrong.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: bash 4.2-2ubuntu2.6
  ProcVersionSignature: Ubuntu 3.2.0-76.111-generic 3.2.66
  Uname: Linux 3.2.0-76-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Tue Mar 17 18:34:25 2015
  InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: bash
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1433155/+subscriptions