Date: Sun, 3 Dec 2000 10:48:17 -0500 (EST) From: Peter Dufault <dufault@hda.com> To: hackers@freebsd.org Subject: Arg! Siginfo and pthreads again Message-ID: <200012031548.KAA61923@hda.hda.com>
next in thread | raw e-mail | index | archive | help
Again I've forgotten that SIGINFO dumps the pthread info and created several gigabytes of /tmp files: > rt% rm /tmp/uthread* > /bin/rm: Argument list too long. I don't consider it bad form to use SIGINFO to see if processes are still around without first installing a SIGINFO handler. Am I the only one ever burnt by this? Do other user-space thread systems handle this similarly? Maybe an info thread can block at an info fifo in conjunction with a "psthread" program. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Fail-Safe systems, Agency approval To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200012031548.KAA61923>