Bug#164697: marked as done (perl: SIGRTMIN not delivered to program started from some perl script)
Your message dated Sat, 18 Dec 2004 20:22:26 +0900
with message-id <81llbvu9zh.wl@omega.webmasters.gr.jp>
and subject line Processed: Re: Bug#164697: not a bug in perl
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--------------------------------------
Received: (at submit) by bugs.debian.org; 14 Oct 2002 15:19:07 +0000
>From oskar@osk.mine.nu Mon Oct 14 10:19:07 2002
Return-path: <oskar@osk.mine.nu>
Received: from as2-1-6.lh.m.bonet.se (alpha) [194.236.130.162] (mail)
by master.debian.org with esmtp (Exim 3.12 1 (Debian))
id 1816zr-00067q-00; Mon, 14 Oct 2002 10:19:07 -0500
Received: from oskar ([192.168.1.2] ident=mail)
by alpha with esmtp (Exim 3.36 #1 (Debian))
id 1816wM-0002bo-00
for <submit@bugs.debian.org>; Mon, 14 Oct 2002 17:15:30 +0200
Received: from usel by oskar with local (Exim 3.36 #1 (Debian))
id 1816zn-0002Pt-00; Mon, 14 Oct 2002 17:19:03 +0200
From: Oskar Liljeblad <oskar@osk.mine.nu>
Subject: perl: SIGRTMIN not delivered to program started from some perl script
To: submit@bugs.debian.org
X-Mailer: bug 3.3.10.2
Message-Id: <E1816zn-0002Pt-00@oskar>
Date: Mon, 14 Oct 2002 17:19:03 +0200
Delivered-To: submit@bugs.debian.org
Package: perl
Version: 5.8.0-13
Severity: normal
I have an application that relies on being able to receive the RTMIN signal.
When run from the shell the signal is delivered normally, but when
the application is started from perl (with system, backticks, open etc),
the signal is not delivered. Other signals (like TERM) are delivered OK,
but not the RTMIN signal.
Here's a test case:
1. Compile this code into the executable "demo":
#include <signal.h>
#include <stdio.h>
static void event_handler(int sig, siginfo_t *si, void *data)
{
printf("received signal=%d\n", sig);
}
int main(int argc, char **argv)
{
struct sigaction act;
act.sa_sigaction = event_handler;
sigemptyset(&act.sa_mask);
act.sa_flags = SA_SIGINFO;
sigaction(SIGRTMIN, &act, NULL);
kill(getpid(), SIGRTMIN);
}
2. Run "demo". The output should be "received signal=32".
3. Now run "perl -e system('demo')". There is no output.
This could be a kernel bug, but an external bug reporter told me
that he didn't experience the problem with perl 5.6.
This might seem like a minimal problem, but it prevents my
program dnotify from being able to run from perl scripts.
Oskar Liljeblad (oskar@osk.mine.nu)
-- System Information
Debian Release: testing/unstable
Kernel Version: Linux oskar 2.4.19 #3 Fri Oct 4 17:30:42 CEST 2002 i686 unknown unknown GNU/Linux
Versions of the packages perl depends on:
ii libc6 2.2.5-15 GNU C Library: Shared libraries and Timezone
ii libdb4.0 4.0.14-1 Berkeley v4.0 Database Libraries [runtime]
ii libgdbmg1 1.7.3-27.1 GNU dbm database routines (runtime version).
ii perl-base 5.8.0-13 The Pathologically Eclectic Rubbish Lister.
ii perl-modules 5.8.0-13 Core Perl modules.
---------------------------------------
Received: (at 164697-done) by bugs.debian.org; 18 Dec 2004 11:22:27 +0000
>From gotom@debian.or.jp Sat Dec 18 03:22:27 2004
Return-path: <gotom@debian.or.jp>
Received: from omega.webmasters.gr.jp (webmasters.gr.jp) [218.44.239.78]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CfcfL-0001ew-00; Sat, 18 Dec 2004 03:22:27 -0800
Received: from omega.webmasters.gr.jp (localhost [127.0.0.1])
by webmasters.gr.jp (Postfix) with ESMTP
id DD7E9DEB58; Sat, 18 Dec 2004 20:22:26 +0900 (JST)
Date: Sat, 18 Dec 2004 20:22:26 +0900
Message-ID: <81llbvu9zh.wl@omega.webmasters.gr.jp>
From: GOTO Masanori <gotom@debian.or.jp>
To: Oskar Liljeblad <oskar@osk.mine.nu>, 164697-done@bugs.debian.org
Cc: Brendan O'Dea <bod@debian.org>
Subject: Re: Processed: Re: Bug#164697: not a bug in perl
In-Reply-To: <handler.s.C.103929698724853.transcript@bugs.debian.org>
References: <20021207213620.GA27916@londo.c47.org>
<handler.s.C.103929698724853.transcript@bugs.debian.org>
User-Agent: Wanderlust/2.9.9 (Unchained Melody) SEMI/1.14.3 (Ushinoya)
FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.2
(i386-debian-linux-gnu) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Delivered-To: 164697-done@bugs.debian.org
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Hi,
At Sat, 07 Dec 2002 15:48:13 -0600,
Debian Bug Tracking System wrote:
> > reassign 164697 libc6
> Bug#164697: perl: SIGRTMIN not delivered to program started from some perl script
> Bug reassigned from package `perl' to `libc6'.
> I have an application that relies on being able to receive the RTMIN signal.
> When run from the shell the signal is delivered normally, but when
> the application is started from perl (with system, backticks, open etc),
> the signal is not delivered. Other signals (like TERM) are delivered OK,
> but not the RTMIN signal.
Thanks for your report - but I didn't notice this bug was reported.
BTW, I think this bug is already fixed in the latest 2.3.2.ds1-19:
gotom@moog:~/debian/glibc/bugs/164697> gcc -o demo demo.c
gotom@moog:~/debian/glibc/bugs/164697> ./demo
received signal=33
gotom@moog:~/debian/glibc/bugs/164697> perl -e "system( 'demo' )"
received signal=33
I close this report. However if you think it's not still fixed,
please reopen this bug and talk to us.
Regards,
-- gotom
Reply to: