HP3000-L Archives

May 2004, Week 3

HP3000-L@RAVEN.UTC.EDU
Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
Re: Our HP3K 969 is misbehaving (Very long)
From:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Fri, 21 May 2004 10:58:56 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (32 lines) 
Re:
> So lets look at a system abort using SAT: for each CPU we want to get a trace.

...
> SYSTEM ABORT 0 FROM SUBSYSTEM 0

unusual, but:

> $6 ($0) nmsat > cpu 2 ; tr,i,d
>        PC=a.0018304c system_abort
> NM* 0) SP=41855428 RP=a.00182dd8 ?system_abort+$8
>          export stub: a.008b61a0 make_pcall_from_debug+$330
> NM  1) SP=41855428 RP=a.007a5d2c func_code_eval+$998
...
> NM  1) SP=418433e8 RP=a.00a5a064 hxdebug+$e4

Points the finger at the user.  He/she deliberately called system_abort
from within Debug/iX.  Generally, that results in a system_abort.

Workaround: don't do that.

:)


--
Stan Sieler
[log in to unmask]
www.allegro.com/sieler/wanted/index.html

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2