Date: Mon, 13 Feb 2006 14:30:09 -0500 From: John Baldwin <jhb@freebsd.org> To: Antoine Brodin <antoine.brodin@laposte.net> Cc: freebsd-sparc64@freebsd.org Subject: Re: sparc64/93226: DEBUG_LOCKS (really stack_save()) causes panics on sparc64 Message-ID: <200602131430.11228.jhb@freebsd.org> In-Reply-To: <20060213193613.547d1b8f.antoine.brodin@laposte.net> References: <200602131150.k1DBo6S1074438@freefall.freebsd.org> <200602131223.51561.jhb@freebsd.org> <20060213193613.547d1b8f.antoine.brodin@laposte.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Monday 13 February 2006 13:36, Antoine Brodin wrote: > 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. magic aside, it would be best to use the same algorithm in both places IMO. It would also be a lot more intuitive to other folks later on. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200602131430.11228.jhb>