<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
It is certainly true that NML might be choking on legitimately bogus
monitor data. However, one hesitates to observe that signaling
incorrect input by crashing is a misfeature...<br>
<br>
The monitor call would be nice to know. You can trap both UUO's and
JSYi on Tops-20 in a number of ways to see what is actually
happening, whether or not you have the source. I can't remember
whether Tops-10 has a similar feature. I thought not, although I'm
fairly certain it does have address break.<br>
<br>
If the crash dump is Galaxy based, then it will have the AC's
preserved in a block in the crash dump.<br>
<div class="moz-cite-prefix">
<hr width="100%" size="2">On 11/10/21 1:11 PM, Robert Armstrong
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:013701d7d65e$5e5b2360$1b116a20$@com">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="Generator" content="Microsoft Word 12 (filtered
medium)">
<style>@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}@font-face
{font-family:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";}tt
{mso-style-priority:99;
font-family:"Courier New";}span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;}span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}span.EmailStyle22
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}span.EmailStyle23
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}div.WordSection1
{page:WordSection1;}</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="color:#1F497D">></span>I don't suppose DEC
supplied source for NML? <span style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="color:#1F497D"> Doesn’t look like it – there’s
nothing in [10,7,NML] except for the NML.EXE. Oddly there
are sources for FAL, NFT and even NCP but not NML. I wonder
if there’s some “trick” for building NML.EXE from some other
source?<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><span
style="color:#1F497D"> In any case, following the rule of
“no matter what bad data you give in the monitor call, it
shouldn’t crash the system” I don’t think NML is the
problem. It might be interesting to figure out exactly what
call NML is trying to execute, but the bug is in the
monitor.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Bob<o:p></o:p><o:p></o:p></span><o:p>
<br>
</o:p></p>
</div>
</blockquote>
</body>
</html>