sparc64/93226: DEBUG_LOCKS (really stack_save()) causes panics on sparc64

[Antoine Brodin]

John Baldwin <jhb at 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