linux-mips
[Top] [All Lists]

Re: looking for help interpreting softlockup/stack trace

To: Ralf Baechle <ralf@linux-mips.org>
Subject: Re: looking for help interpreting softlockup/stack trace
From: Thiemo Seufer <ths@networkno.de>
Date: Thu, 7 Aug 2008 16:19:20 +0200
Cc: David Daney <ddaney@avtrex.com>, Chris Friesen <cfriesen@nortel.com>, linux-mips@linux-mips.org
In-reply-to: <20080807134323.GA15703@linux-mips.org>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <48989AFE.5000500@nortel.com> <20080805191618.GB8629@linux-mips.org> <4899F41C.5070401@avtrex.com> <20080807134323.GA15703@linux-mips.org>
Sender: linux-mips-bounce@linux-mips.org
User-agent: Mutt/1.5.18 (2008-05-17)
Ralf Baechle wrote:
> On Wed, Aug 06, 2008 at 11:57:32AM -0700, David Daney wrote:
> 
> >>> In the trace below, is "epc" the program counter at the time of the   
> >>> timer interrupt?  How does "ra" fit into this, given that the 
> >>> function  whose address it contains isn't seen in the stack trace 
> >>> until quite a  ways down?
> >>
> >> $LBB378 is an internal symbol.  The value of RA may not be very informative
> >> if it was overwritten by a random subroutine call.
> >>
> >
> > I have thought about eliminating these internal labels when the module's 
> > symbols are read.  Would this make any sense?
> 
> I think so.  Maybe that could even be done when the module is linked.  I
> don't think there are ever any relocations against these local symbols.
> Thiemo?

AFAIR all such symbols are branch labels or debug info labels, the module
loader should never use them. (But I don't know if kgdb uses them.)


Thiemo

<Prev in Thread] Current Thread [Next in Thread>