RE: : GC 7.2e: crash in threadkey_test under FreeBSD

I would look at the info and context arguments, and see if it's possible to determine anything else about this signal.  If things are as they appear, this seems like a kernel bug.  As far as I can tell, if a signal handler is invoked, the first argument is required to be one of the signals for which the handler was registered; zero is not allowed by Posix.  My guess is either:

a) The stack trace is incorrect, or
b) This signal was generated at a particularly inopportune time, for the kernel or libc, and the handler did not get invoked correctly due to a FreeBSD bug.

Hans 

> -----Original Message-----
> From: gc-bounces-V9/[email protected] [mailto:gc-bounces-V9/[email protected]]
> On Behalf Of Vitaly Magerya
> Sent: Wednesday, November 20, 2013 11:38 AM
> To: Ivan Maidanski
> Cc: gc-V9/[email protected]
> Subject: Re: [Gc]: GC 7.2e: crash in threadkey_test under FreeBSD
> 
> Ivan Maidanski wrote:
> > I think it is better to fix thread-local support instead of just
> hiding the problem.
> >
> > Could anyone explain how is GC_suspend_handler called with signum=0 ?
> 
> I, for one, have no clue.
> Any idea of how one might debug this?
> _______________________________________________
> Gc mailing list
> Gc-V9/[email protected]
> http://www.hpl.hp.com/hosted/linux/mail-archives/gc/