28 May
2003
28 May
'03
9:24 a.m.
Brian Hechinger wrote:
Sometimes that's a good thing. It may actually be pointing right at
the problem, but hiding it under a mass of additional messages.
On Wed, May 28, 2003 at 02:49:27PM -0600, Kevin Handy
wrote:
Odd. If you can still Control/E to the prompt, try 'N' for several
instructions
to see if it is stuck in VMS's idle loop (cycles through a very small number
of instructions). If it is, it might not be seeing any interrupts.
If Control/E doesn't work, then things are really hosed.
Does simh crash, or does it just do wacky things?
More details would
be useful.
it stops responding. if i don't clear out my nvram file, it fails on memory
check the next time i boot the cpu.
i need to delete the nvram file and restart, then it works. for a while
anyway, and then eventually stops responding.
I haven't been using a NVR file, and it seems to work ok.
Try commenting it out in your configuration file, and see what happens.
It's
probably mostly done with some version of GCC, but I believe that
it is often compiled using Microsoft Visual C.
it's been added to my LONG list of things to clean up for building with
non-gcc. MIPSpro being very anal complains a LOT about the source code.
i'd love to, but i'm not even sure how to. ;(
I've done it using the 'N' command (next instruction), trying to trace
out
bad instructions, and using gdb. It's very tedius when you are looking for
one instruction out of a million executed that are wrong.