It COULD be related to KSE if I've broken some signal delivery types..
do we have a signal guru in the house that can run a diagnostic on
On Sun, 30 Jun 2002, Bill Huey wrote:
> On Mon, Jul 01, 2002 at 07:11:31AM +0200, Michael Nottebrock wrote:
> > Program received signal SIGSEGV, Segmentation fault.
> > 0x281cc918 in _thread_kern_sched_state_unlock () from /usr/lib/libc_r.so.5
> > (gdb) bt
> > #0 0x281cc918 in _thread_kern_sched_state_unlock () from
> > /usr/lib/libc_r.so.5
> > #1 0x281cc2e2 in _thread_kern_scheduler () from /usr/lib/libc_r.so.5
> > #2 0xd0d0d0d0 in ?? ()
> > #3 0x080570b0 in ?? ()
> This is unlikely to be a KSE problem.
> What do the rest of the threads look like ?
> Try "info threads" in gdb and then progressively walking through the thread
> list with "thread N", N being the thread number. I ran into a funny
> create at thread start up time crash and I'm wondering if it could
> be the same thing.
> To Unsubscribe: send mail to [EMAIL PROTECTED]
> with "unsubscribe freebsd-current" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message