From: Thiemo Seufer <ths@networkno.de>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: David Daney <ddaney@avtrex.com>,
Chris Friesen <cfriesen@nortel.com>,
linux-mips@linux-mips.org
Subject: Re: looking for help interpreting softlockup/stack trace
Date: Thu, 7 Aug 2008 16:19:20 +0200 [thread overview]
Message-ID: <20080807141920.GA27494@networkno.de> (raw)
In-Reply-To: <20080807134323.GA15703@linux-mips.org>
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
next prev parent reply other threads:[~2008-08-07 14:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-05 18:25 looking for help interpreting softlockup/stack trace Chris Friesen
2008-08-05 19:11 ` Kaz Kylheku
2008-08-05 19:11 ` Kaz Kylheku
2008-08-05 21:38 ` Chris Friesen
2008-08-05 19:16 ` Ralf Baechle
2008-08-06 18:35 ` Chris Friesen
2008-08-06 18:57 ` David Daney
2008-08-07 13:43 ` Ralf Baechle
2008-08-07 14:19 ` Thiemo Seufer [this message]
2008-08-07 21:57 ` David Daney
2008-08-05 20:28 ` Chad Reese
2008-08-05 20:46 ` Chris Friesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080807141920.GA27494@networkno.de \
--to=ths@networkno.de \
--cc=cfriesen@nortel.com \
--cc=ddaney@avtrex.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.