Date: Fri, 31 Jan 2003 09:38:26 -0800 From: Peter Wemm <peter@wemm.org> To: John Polstra <jdp@polstra.com> Cc: ia64@freebsd.org Subject: Re: Far enough along for a CVSup port? Message-ID: <20030131173826.7DDC42A8A1@canning.wemm.org> In-Reply-To: <200301311700.h0VH0RZk073550@vashon.polstra.com>
next in thread | previous in thread | raw e-mail | index | archive | help
John Polstra wrote:
> In article <20030131030631.0B8A72A89E@canning.wemm.org>,
> Peter Wemm <peter@wemm.org> wrote:
> > dmesg reports all the userland crashes:
> >
> > fatal user trap (cpu 0):
> >
> > trap vector = 0x14 (Page Not Present)
> > cr.iip = 0x60000000402cfa50
> > cr.ipsr = 0x1013080a6010 (mfl,ic,i,dt,dfh,rt,cpl=3,it,ri=0,bn)
> > cr.isr = 0x400000000 (code=0,vector=0,r,ei=0)
> > cr.ifa = 0xdc9a8
> > cr.iim = 0x3c00e
> > curthread = 0xe00000003e390a80
> > pid = 66468, comm = paramtest
> >
> > Here's how to read it:
> > iip == program counter which points to the instruction bundle
> > ipsr == equivalent of eflags. There's some interesting stuff in here, and
> > some not-so-interesting stuff. Of note, ri=[012] which indicates which
> > instruction in the current bundle is the one faulting or to be resumed to
.
> > ifa == virtual fault address
>
> Thanks for the explanation. That's good enough for me to at least
> give it a try. If I get totally stuck, I can always put it on hold
> until gdb comes along. (Notice how I carefully avoid volunteering to
> do the gdb port ...)
Yeah, and you've probably noticed the deathly silence here when the
subject of the gdb port came up. :-/ I think I might do some trolling
and see if I can find somebody who knows what to do..
Cheers,
-Peter
--
Peter Wemm - peter@wemm.org; peter@FreeBSD.org; peter@yahoo-inc.com
"All of this is for nothing if we don't go to the stars" - JMS/B5
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-ia64" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030131173826.7DDC42A8A1>