Re: [PATCH] Always send siginfo for synchronous signals

[Jeremy Fitzhardinge]

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@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/