T.R | Title | User | Personal Name | Date | Lines |
---|
1715.1 | | TOOK::SWIST | Jim Swist LKG2-2/T2 DTN 226-7102 | Fri Oct 25 1991 09:31 | 9 |
| "Doctor, it hurts when I twist my arm backwards..."
Don't twist your arm backwards. Some of the MCC_LOG and MCC_IM_LOG
bits activate private internal debugging routines which can be
hazardous to your health. In particular, some of the IM log bits will
cause the intentional corruption of the dispatch table in order to test
the code which detects corruption!
I'm surprised anything worked when you turned them all on.
|
1715.2 | How can I be sure all is OK? | CUJO::HILL | Dan Hill-Net.Mgt.-Customer Resident | Fri Oct 25 1991 22:34 | 8 |
| Oops. I was told to turn everything on as part of troubleshooting the
problem mentioned in note 1687.1 . I've gotten the occassional
"strange" error message since then (��No such DNS entity messages)
which indicate that developers should check their code.
How do you suggest that I ensure that all is OK?
-Dan
|
1715.3 | | TOOK::SWIST | Jim Swist LKG2-2/T2 DTN 226-7102 | Mon Oct 28 1991 08:46 | 4 |
| Delete your dispatch table file and re-enroll everything. Send mail
to t_hupper (took::) and ask him to give you more details on what the
MCC_IM_LOG bits do to you.
|