One of the developers here reports the following - is there a patch known?
Many thanks; I'll summarize.
Pat Wilson
paw_at_dartmouth.edu
------- Forwarded Message
I've run into a problem with DECthreads and disassociated programs:
There is a problem with the pthread libraries in DU 4.0B. If an
exception isn't handled by code in the program, the DECthreads code
can end up writing the following sort of message out fd 1 or 2 (stdout
or stderr). If the program has disassociated from its control
terminal, then fds 1 and 2 may be in use for other purposes (e.g. as
sockets), quite possibly in situations where the following message
causes some sort of problem for the program at the other end of the
socket. I will probably add code to my program to open fds 1 and 2 to
/dev/null or some such, but I really don't think a system library
should write to stdout or stderr in any circumstances. If it needs to
do something, perhaps syslog(3) would be a reasonable alternative.
DECthreads Last Chance handler: thread 1 exiting on status exception 0x177db005
Exception: Invalid memory address (dce / thd)
- -Eric Bivona
Information Systems, Dartmouth College
------- End of Forwarded Message
Received on Wed Feb 19 1997 - 22:25:39 NZDT