MOL crash: Instruction Pointer not in ROM/RAM

Samuel Rydh mol-general@lists.maconlinux.org
Wed, 12 Feb 2003 14:02:01 +0100


On Tue, Feb 11, 2003 at 05:31:52PM -0600, Rob Latham wrote:
> I had mol running macosX 10.2.3 for a while, not doing a whole lot (i
> think macosX was sleeping).   It crashed with the single line 
> 
> Instruction Pointer not in ROM/RAM (nip 4846DF04, nip_phys 4846DF04)
> 
> and i'd like to know how to debug the 'nip' and 'nip_phys' values, if
> it's possible to decode those into anything meaninful. 

MOL is off fetching instructions not located in RAM. Unfortunately,
the nip value does not tell you much though (looks like
garbage).

If MOL runs in debugger mode, then MOL breaks into the
debugger instead of exiting (it might be possible to
deduce what went wrong). A lot of different things could
lead to this problem though (a bug in MOL, a bug in OSX or a bug
in the linux kernel).

If this problem is reproducible, I'd like to hear about it.

/Samuel