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: [EMAIL PROTECTED]
> Delivery-date: Thu, 28 Oct 1999 09:32:28 -0600
> Date: Thu, 28 Oct 1999 11:31:07 -0400 (EDT)
> From: Daniel Eischen <[EMAIL PROTECTED]>
>
> > 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
> [EMAIL PROTECTED]
>
--
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 [EMAIL PROTECTED]
Albuquerque, NM 87131 http://www.eece.unm.edu/~dbader
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
