From owner-freebsd-hackers  Tue Jun  8 15: 1:53 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3])
	by hub.freebsd.org (Postfix) with ESMTP id 53EB314E1F
	for <hackers@FreeBSD.ORG>; Tue,  8 Jun 1999 15:01:49 -0700 (PDT)
	(envelope-from eischen@vigrid.com)
Received: (from eischen@localhost)
	by pcnet1.pcnet.com (8.8.7/PCNet) id SAA25453;
	Tue, 8 Jun 1999 18:01:00 -0400 (EDT)
Date: Tue, 8 Jun 1999 18:01:00 -0400 (EDT)
From: Daniel Eischen <eischen@vigrid.com>
Message-Id: <199906082201.SAA25453@pcnet1.pcnet.com>
To: dan@trinsec.com, hackers@FreeBSD.ORG
Subject: Re: Segfault in longjmp() ?
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Dan Moschuk wrote:
> The machine is a SMP 3.0-RELEASE box.
>
> A heavily threaded program is segfaulting in the longjmp() function.
> Any ideas what would cause this?

Libc_r or Linuxthreads?

There are some known problems WRT signal handling in libc_r.  I
think they've been mostly fixed (with possible exception of
signals interrupting signal handlers) with the changes at:

  ftp://ftp.pcnet.com/users/eischen/FreeBSD/uthread.tgz

If you're having problems with libc_r and these changes don't
solve your problem, let me know.  Make sure you do a 'make clean'
in src/lib/libc_r before building.

Dan Eischen
eischen@vigrid.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message