Subj : How to diagnose/resolve libthread panic?
To   : comp.programming.threads
From : Paul F. Pearson
Date : Thu Jun 02 2005 04:01 pm

Hi,

I've searched Google, and this group specifically, and can't find any
good pointers on how to identify what's causing a libthread panic.
Could someone point me in the right direction?

Specifically, the panic is occurring in a mostly-Ada program (with some
C linked in) on Solaris 8, patches up-to-date as of a couple of months
ago.  Our compiler is gnat 3.15p1, and the C code is compiled using the
gcc included in that gnat.  The process usually has about 277 lwps
running.  We're using the Solaris native threads.  The problem isn't
vert repeatable, but happens just often enough to be troubling.

I don't have handy the specific output of the libthread panic, but it's
a SIGSEGV (signal 1).

So, how does one go about diagnosing a problem of this sort?  Is there
a way to trap the panic?  What are the common causes?  Right now, our
hope is to put in "hooks" and run with them, hoping the panic happens
and we can see what's going on.  We just don't know how to go about
putting in the "hooks".

As I said, if there's a good "start here" site and/or book, I'll be
glad to RTFM.  If a more Solaris-centric newsgroup is more appropriate,
then I'll gladly go there.

Thanks in advance.

.