Message-ID: <421D24BD.1090307@goop.org>
Date: Wed, 23 Feb 2005 16:50:05 -0800
From: Jeremy Fitzhardinge <jeremy@goop.org>
User-Agent: Mozilla Thunderbird  (X11/20041216)
MIME-Version: 1.0
To: Chris Wright <chrisw@osdl.org>
Cc: Roland McGrath <roland@redhat.com>,
       Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
       Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] Always send siginfo for synchronous signals
References: <421C25BE.1090700@goop.org> <20050223201903.GF21662@shell0.pdx.osdl.net> <421D0D3F.40902@goop.org> <20050223234626.GZ15867@shell0.pdx.osdl.net>
In-Reply-To: <20050223234626.GZ15867@shell0.pdx.osdl.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1094
Lines: 35

Chris Wright wrote:

>>/proc/N/status will tell you that a process has
>>a signal pending, but it won't tell you how many are pending).
>>    
>>
>
>Suggestion for good place to display that info?
>  
>
I guess another line in /proc/N/status:

    SigQue: 0 0 0 0 0 0 0 123 0 0 1238 0 0 0 0 0 ... 0 0 1

or something, but I haven't really thought about it.

>>In fact, bugs with these symptoms have been reported against Valgrind
>>from time to time for years, and its only recently I worked out what's
>>going on (mostly because I introduced a bug which caused Valgrind to do
>>it to itself).
>>    
>>
>This code is pretty new (since 2.6.8-rc1, last June), so I expect some
>other issue in the years past.
>  
>
There was always a limit on the number of pending queue siginfo
signals.  It used to be system-wide rather than per-user though.

    J
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/