| T.R | Title | User | Personal Name
 | Date | Lines | 
|---|
| 1452.1 | Random memory corruptors or possibly worse. | WTFN::SCALES | Despair is appropriate and inevitable. | Fri Dec 13 1996 16:59 | 23 | 
| 1452.2 | Customer's reply and some comments of my own. | PEACHS::LAMPERT | Pat Lampert, UNIX  Applications Support,  343-1050 | Fri Dec 20 1996 16:38 | 115 | 
| 1452.3 | I guess I might as well ask here. | PEACHS::LAMPERT | Pat Lampert, UNIX  Applications Support,  343-1050 | Fri Dec 20 1996 17:06 | 3 | 
| 1452.4 | Should I ipmt this? | PEACHS::LAMPERT | Pat Lampert, UNIX  Applications Support,  343-1050 | Fri Dec 27 1996 19:41 | 6 | 
| 1452.5 | PLEASE DON'T SEND NOTES VERBATIM TO CUSTOMERS. | WTFN::SCALES | Despair is appropriate and inevitable. | Fri Jan 03 1997 16:03 | 35 | 
| 1452.6 | Thanks. | PEACHS::LAMPERT | Pat Lampert, UNIX  Applications Support,  343-1050 | Mon Feb 03 1997 12:30 | 15 | 
|  | Sorry I didnt see this reply until today.
As for the forwarding of notes, my appologies; I will re-phrase
things in the future. 
I will pass on the fact that you cannot dynamically load the 
thread / exc libraries. I can intuitively understand why this 
would be a problem, but can you point me to any release 
note / documentation which documents this  restriction? 
I cant seem to find anything. About all I can say right now is 
that the man pages specifically say you must link a certain way, 
and never discuss dynamic loading.
Pat
 | 
| 1452.7 | See digital_unix note 4171.1 | PEACHS::LAMPERT | Pat Lampert, UNIX  Applications Support,  343-1050 | Tue Feb 04 1997 14:07 | 5 | 
|  | To answer my own question; I just stumbled across a note in the
digital_unix conference which provides enough explaination for 
me.
Pat
 |