From: Johannes Stoelp <Johannes.Stoelp@synopsys.com>
To: Yao Qi <qiyaoltc@gmail.com>,
Johannes Stoelp <Johannes.Stoelp@synopsys.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>,
Andreas Ropers <Andreas.Ropers@synopsys.com>,
Marc Mones <Marc.Mones@synopsys.com>,
"Kai Schuetz" <Kai.Schuetz@synopsys.com>,
Johannes Stoelp <Johannes.Stoelp@synopsys.com>
Subject: RE: Infinite Stack Unwinding ARM
Date: Tue, 11 Apr 2017 16:20:00 -0000 [thread overview]
Message-ID: <6ECCE8A0904A1643BE093611EF2098CE0147592C@DE02WEMBXB.internal.synopsys.com> (raw)
In-Reply-To: <8660iclbdo.fsf@gmail.com>
Hi Yao,
Yao Qi <qiyaoltc@gmail.com> writes:
> We may end up with having some Linux kernel specific stuff, and this should fall in "Linux kernel debugging for aarch64".
I see, thanks for the hint.
> Can you post me the backtrace, as a sample output?
When having unlimited backtrace enabled (default), I get backtraces like the following:
#0 gic_handle_irq (regs=0xffffffc07d9c7e30) at drivers/irqchip/irq-gic.c:263
#1 0xffffffc000083ce4 in el1_irq () at arch/arm64/kernel/entry.S:346
#2 0xffffffc000083ce4 in el1_irq () at arch/arm64/kernel/entry.S:346
#3 0xffffffc000083ce4 in el1_irq () at arch/arm64/kernel/entry.S:346
#4 0xffffffc000083ce4 in el1_irq () at arch/arm64/kernel/entry.S:346
#5 0xffffffc000083ce4 in el1_irq () at arch/arm64/kernel/entry.S:346
#6 0xffffffc000083ce4 in el1_irq () at arch/arm64/kernel/entry.S:346
#7 0xffffffc000083ce4 in el1_irq () at arch/arm64/kernel/entry.S:346
...
#20009 0xffffffc000083ce4 in el1_irq () at arch/arm64/kernel/entry.S:346
#20010 0xffffffc000083ce4 in el1_irq () at arch/arm64/kernel/entry.S:346
#20011 0xffffffc000083ce4 in el1_irq () at arch/arm64/kernel/entry.S:346
#20012 0xffffffc000083ce4 in el1_irq () at arch/arm64/kernel/entry.S:346
#20013 0xffffffc000083ce4 in el1_irq () at arch/arm64/kernel/entry.S:346
#20014 0xffffffc000083ce4 in el1_irq () at arch/arm64/kernel/entry.S:346
...
Best,
Johannes
prev parent reply other threads:[~2017-04-11 16:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 12:54 Johannes Stoelp
2017-04-05 11:09 ` Yao Qi
2017-04-07 7:15 ` Johannes Stoelp
2017-04-08 5:00 ` Duane Ellis
2017-04-10 12:01 ` Yao Qi
2017-04-11 16:20 ` Johannes Stoelp [this message]
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=6ECCE8A0904A1643BE093611EF2098CE0147592C@DE02WEMBXB.internal.synopsys.com \
--to=johannes.stoelp@synopsys.com \
--cc=Andreas.Ropers@synopsys.com \
--cc=Kai.Schuetz@synopsys.com \
--cc=Marc.Mones@synopsys.com \
--cc=gdb@sourceware.org \
--cc=qiyaoltc@gmail.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox