From owner-freebsd-hackers Thu Oct 28 8:37: 0 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from cielo.eece.unm.edu (cielo.eece.unm.edu [129.24.24.11]) by hub.freebsd.org (Postfix) with ESMTP id 6EAA814DAB for ; Thu, 28 Oct 1999 08:36:58 -0700 (PDT) (envelope-from dbader@eece.unm.edu) Received: from jalapeno.eece.unm.edu ([129.24.24.88] helo=eece.unm.edu) by cielo.eece.unm.edu with esmtp (Exim 2.12 #1) id 11grbl-0006VP-00; Thu, 28 Oct 1999 09:36:57 -0600 Received: (from dbader@localhost) by eece.unm.edu (8.9.3+Sun/8.9.1) id JAA05245; Thu, 28 Oct 1999 09:36:52 -0600 (MDT) Date: Thu, 28 Oct 1999 09:36:52 -0600 (MDT) Message-Id: <199910281536.JAA05245@eece.unm.edu> X-Authentication-Warning: jalapeno.eece.unm.edu: dbader set sender to dbader@eece.unm.edu using -f From: "David A. Bader" To: eischen@vigrid.com Cc: freebsd-hackers@FreeBSD.ORG In-reply-to: <199910281531.LAA14271@pcnet1.pcnet.com> (message from Daniel Eischen on Thu, 28 Oct 1999 11:31:07 -0400 (EDT)) Subject: Re: POSIX threads References: <199910281531.LAA14271@pcnet1.pcnet.com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I'm familiar with LinuxThreads libc_r that uses BOTH SIGUSR1 and SIGUSR2. I recently took code that used to work with FSU's implementation of threads under FreeBSD; and instead recompiled with the new FreeBSD 3.x threads; however, it crashes now when creating threads. The FSU threads (that used to work with FreeBSD 2.x no longer compile under 3.x); so I'm not sure if there's another implementation I can try. Thanks, -david > Envelope-to: dbader@eece.unm.edu > Delivery-date: Thu, 28 Oct 1999 09:32:28 -0600 > Date: Thu, 28 Oct 1999 11:31:07 -0400 (EDT) > From: Daniel Eischen > > > I have an application that uses SIGUSR1, but also POSIX threads. It > > appears (?) that the user-level POSIX threads now incorporated into > > FreeBSD 3.x use SIGUSR1 and SIGUSR2. Is this correct? If so, and I > > have a threaded application, what signals are still available for use? > > No, the threads library that comes with 3.x/4.x does not use SIGUSR1 > or SIGUSR2 for anything. It does use SIGPROF via setitimer for its > internal scheduling mechanism, and SIGINFO to dump thread information > (to aid debugging), but the other signals are available. > > Perhaps you're confusing libc_r with LinuxThreads which also runs > under FreeBSD. I believe LinuxThreads uses SIGUSR1 and/or SIGUSR2. > > Dan Eischen > eischen@vigrid.com > -- David A. Bader, Ph.D. Office: 505-277-6724 Dept of Electrical and Computer Engineering FAX: 505-277-1439 EECE Building University of New Mexico dbader@eece.unm.edu Albuquerque, NM 87131 http://www.eece.unm.edu/~dbader To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message