Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 23 Jan 2001 20:00:38 -0500 (EST)
From:      Andrew Gallatin <gallatin@cs.duke.edu>
To:        Bernd Walter <ticso@cicely5.cicely.de>
Cc:        freebsd-alpha@FreeBSD.ORG
Subject:   Re: -current failing on PC164
Message-ID:  <14958.10234.43199.492866@grasshopper.cs.duke.edu>
In-Reply-To: <20010124010535.A29018@cicely5.cicely.de>
References:  <20010123214322.A26643@cicely5.cicely.de> <20010124010535.A29018@cicely5.cicely.de>

next in thread | previous in thread | raw e-mail | index | archive | help

Bernd Walter writes:
 > >     trap entry = 0x4 (unaligned access fault)
 > >     a0         = 0xfffffc000055eec7
 > >     a1         = 0x29
 > >     a2         = 0x14
 > >     pc         = 0xfffffc00003a3270
 > >     ra         = 0xfffffc00003a3258
 > >     curproc    = 0xfffffc00005d3038
 > >         pid = 0, comm = 
 > > 
 > > Stopped at      0xfffffc00003a3270:     ldl     t0,0x8(s0) <0xfffffc00005bb568> <t0=0xfffffc000055ee9f,s0=0xfffffc00005bb560>
 > > db> trace
 > > (null)() at 0xfffffc00003a3270
 > 
 > After removing several debugging options from the kernel such as
 > mutex_debug, ktr, ... it finaly booted.
 > I recheck if I didn't made something wrong with them although the
 > config worked with an earlier source.

If you'd care to try to debug this further, that would be great.
You should add back the failing options to a test kernel, configure it 
with -g so as to get a kernel.debug with symbols, boot it, and note
the faulting pc.

Then run gdb on kernel.debug and say "l *<faulting pc>"  Eg:

(kgdb) l *0xfffffc00003a3270

This should display the problematic line of source code.

Thanks!

Drew


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-alpha" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?14958.10234.43199.492866>