From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Jon Ringle <jon.ringle@comdial.com>, gdb@sources.redhat.com
Subject: Re: Infinite backtrace on arm
Date: Mon, 27 Oct 2003 15:21:00 -0000 [thread overview]
Message-ID: <3F9D3812.2090801@redhat.com> (raw)
In-Reply-To: <20031027145320.GA26422@nevyn.them.org>
> The problem is that there's not much GDB can do with hand-coded
> assembly functions.
>
> However, GDB ought to be able to detect and stop that loop without any
> of this. It seems to me that the problem is not two frames with the
> same PC, but two frames with their PC "saved" in the same place - i.e.
> GDB failing to figure out where the PC is saved. This is made a little
> tricky in current versions of GDB, because the PC is normally unwound
> using frame_pc_unwind (which doesn't tell us where it was saved, since
> the interface doesn't assume it's a single normal register), and the
> core code doesn't have a concept of a "PC register" any more.
>
> Andrew, any idea on how to do this?
Before anything else, find out what a current GDB does - its code to
detect a "corrupt stack" is now much improved.
Andrew
next prev parent reply other threads:[~2003-10-27 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-26 4:28 Jon Ringle
2003-10-27 14:53 ` Daniel Jacobowitz
2003-10-27 15:21 ` Andrew Cagney [this message]
2003-10-27 15:23 ` Daniel Jacobowitz
2003-10-27 16:01 Jon Ringle
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=3F9D3812.2090801@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=jon.ringle@comdial.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