Re: Anyone with a QDSS equipped machine

[Mouse <mouse%Rodents-Montreal.ORG@localhost>]

>>     stray interrupt: vector 0x10, ipl 31

> I don't know whether this is the case here, but SCB vector 0x10 is
> "Privileged Instruction fault".

> IIRC the "stray interrupt" prints out the offset from beginning of
> the SCB.

> So, it might be something completely different?

I don't have the source on hand for that version.  But what I do have
on hand says

scb_stray(void *arg)
{
...
	vector = ((int) arg) & ~3;
...
		printf("stray interrupt: vector 0x%x, ipl %d\n", vector, ipl);

so, assuming that code remains operationally unchanged, the value
printed appears to be the byte offset from the SCBB.

My VARM transcription says that offset 0x10 is for "reserved or
privileged instruction" fault.  If the SCB is seen as array of
longwords, the vector at [0x10] is at offset 0x40, which is the CHMK
handler.  I find the former far more plausible, not to mention a better
fit for the code probably responsible for the printf.

I didn't get the original list mail.  Looking at it via mail-index, I
don't see any obvious reason why not, but, because the archive doesn't
show headers, that means little.  Since the issue arises with a
simulator, I would suggest either using a debugger on the simulator or
adding debugging code, in either case to identify exactly what is
producing the relevant trap/fault.

I also will add to-do items for myself for adding QVSS and QDSS support
to my MicroVAX-II emulator.  No idea when I might get around to either.

/~\ The ASCII				  Mouse
\ / Ribbon Campaign
 X  Against HTML		mouse%rodents-montreal.org@localhost
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B