Nerds!!!

8-)

Ray Shahan

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
Behalf Of Bill Cadier
Sent: Thursday, April 27, 2006 3:14 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] Debugging forgetfulness

Jeff writes:

> Just ran across this program abort which has me a bit stumped... I
have
> :setdump enabled but can't get a typical trace that I could track down
> to a code location.  This is all I get:
> 
> > **** Illegal instruction address (TRAPS 56).
> >  
> > ABORT: RAPGEN39.RAP.DEV
> > Can't unwind.  Address has no unwind entry.  (error #1905)
> > Can't load top frame.  TR/LEV won't work here.  (error #1913)
> >
> > R0 =00000000 000003ff 2d2d2d5f 000007d0 R4 =d96a5f90 d96a7f90
00000000
> > 00000000
> > R8 =00000000 00000000 00000000 00000000 R12=00000000 00000000
00000000
> > 00000000
> > R16=00000000 00000000 00000000 4187480c R20=4187480c 00000300
7fffff07
> > 000000ff
> > R24=00000003 4165224c 41874714 41677000 R28=000000f8 7fffffff
418747f0
> > 00000002
> >
> > IPSW=00047d0f=westhlnxbCvmofrQPDI PRIV=3
> >  SAR=10  PCQF=f9.2d2d2d5f  f9.2d2d2d63
> >
> > SR0=0000000a 00000000 00000000 00000000 SR4=000000f9 000006e5
0000000b
> > 0000000a
> > TR0=00000000 00d39b00 0083dcec 41876d70 TR4=00000000 41875c1c
0036d734
> > 0000000f
> > PID1=00000a7a=0000053d(W)               PID2=00000000=00000000(W)
> > PID3=00000000=00000000(W)               PID4=00000000=00000000(W)
> > PID5=00000000=00000000(W)               PID6=00000000=00000000(W)
> > PID7=00000000=00000000(W)               PID8=00000000=00000000(W)
> >
> > RCTR=00000000 ISR=1004007d IOR=0607480c IIR=43ffff80 IVA=00146000
> > ITMR=cca3d349
> > EIEM=ffffffff EIRR=00000000 CCR=c0 SCR=0
> Anyone offer a clue? 
> 
> Jeff

ISR=1004007d IOR=0607480c IIR=43ffff80

The interrupt space register looks a little funky, 1004007d so what
probably happened is that the stack frame got walked on and when the
procedure exited things wound up this way. Trying to execute code at
1004007d.0607480c would definitely be an illegal instruction address.

If you dump out a blob of stuff around the SP register when this trap
happens you might ID some ASCII data that could give a hint as to where
this is happening. Or you could use the old "add displays" (or printf's
or writeln's) method of debugging which is quite effective in this
situation :-)

hth,

Bill
hp/vCSY

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

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