yea, emul_netbsd_aoutm68k_object is just the symbol with the largest address.
you can make it not print nonsense like that by setting db_maxoff to something
smaller (or "set $maxoff = ..." in ddb).

-Chuck


On Mon, Dec 13, 2004 at 11:43:02PM +0100, Christian Groessler wrote:
> Hi,
> 
> I'm trying to build a 2.0 kernel on a Centris 650, 24MB.
> The kernel currently running is 2.0, cross compiled from Linux/i386.
> 
> Here is a ddb session:
> 
> NetBSD/mac68k (mac68k) (console)
> 
> login: uvm_fault(0x172b90, 0xd61a4000, 0, 0x1) -> 0xe
...
> panic: MMU fault
> Stopped in pid 1808.1 (cc1) at  netbsd:cpu_Debugger+0x6:        unlk    a6
> db> trace
> cpu_Debugger(2000,8,826eac,826e98,126fd4) + 6
> panic(146b10,2c,4,0,91f40) + f8
> trap(8,5e6,d61a4100) + 24e
> emul_netbsd_aoutm68k_object(1fe0202c,0,97fe8,96000,95eb0) + d6007454
> ?() at 7
...
> 
> Hmm, this emul_netbsd_aoutm68k_object doesn't seem to be correct. I
> will cross build a kernel with "-g" and run it again. Maybe then there
> is more information.
> 
> regards,
> chris