[lkml]   [2009]   [Mar]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: RT signal queue overflow (Was: Q: SEGSEGV && uc_mcontext->ip (Was: Signal delivery order))

On Wed, 18 Mar 2009, Gábor Melis wrote:
> It was just a month or so ago when I finally made to change to use a
> non-real-time signal for signalling stop-for-gc.

Ahh, and that is when you noticed the issue with SIGSEGV?

One thing you might try is to still use a non-real-time signal, but simply
depend on the fact that signals are basically peeled off the signal
bitmask in a signal number order (with the exception that fatal signals
are handled specially).

IOW, on x86, just about the _only_ normal user-generated signal that can
happen before SIGSEGV is SIGUSR1, because SIGSEGV is 11, and SIGUSR1 is

If you were to use SIGUSR2 (signal #12) you'd probably never see this.

Of course, there are other signals with numbers < 11, but they are
generally meant for other synchronous traps (ie signals like
SIGTRAP/AIGABRT/SIGFPE/SIGBUS), or for killing the process (signals

So maybe you'd be happy with just picking another signal? It's not a
_pretty_ solution, but it should work across most kernel versions.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2009-03-18 16:01    [W:0.055 / U:0.960 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site