Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 13 Feb 2006 19:36:13 +0100
From:      Antoine Brodin <antoine.brodin@laposte.net>
To:        John Baldwin <jhb@freebsd.org>
Cc:        freebsd-sparc64@freebsd.org
Subject:   Re: sparc64/93226: DEBUG_LOCKS (really stack_save()) causes panics on sparc64
Message-ID:  <20060213193613.547d1b8f.antoine.brodin@laposte.net>
In-Reply-To: <200602131223.51561.jhb@freebsd.org>
References:  <200602131150.k1DBo6S1074438@freefall.freebsd.org> <200602131223.51561.jhb@freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin <jhb@freebsd.org> wrote:
> If there are kernel functions before the assembly ones (dependent on link 
> order) then this would wrongly bail when it hit those.  I think you need to 
> do what the ddb stack tracing code does which is to lookup the symbol name 
> and do a bcmp() on the first 4 chars to recognize trapframes.

I ran objdump -d on a sparc64 kernel and it looks like tl0_* and tl1_*
are always at the beginning of the code, there is some kind of magic.

Cheers,

Antoine



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