From: Joel Brobecker <brobecker@adacore.com>
To: Yao Qi <qiyaoltc@gmail.com>
Cc: Martin Simmons <martin@lispworks.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Prevent internal-error when computing $pc in ARM assembly code
Date: Mon, 15 Jun 2015 13:36:00 -0000 [thread overview]
Message-ID: <20150615133613.GE25717@adacore.com> (raw)
In-Reply-To: <86wpz5s31d.fsf@gmail.com>
> > It would be good to have a few more details about what causes us
> > to be in a situation where we'd be failing to read memory at
> > an address. Perhaps just showing the disassembled code and
> > a quick explanation of what happens might be sufficient.
>
> I agree with Joel that we need more details about the problem you are
> trying to fix.
I think the problem comes from improper unwinding of a function
having an unusual frame, causing us to use a bogus return address
which could be anywhere, including in an unreadable memory area.
--
Joel
prev parent reply other threads:[~2015-06-15 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 9:49 Martin Simmons
2015-06-09 18:44 ` Joel Brobecker
2015-06-11 17:25 ` Martin Simmons
2015-06-12 13:21 ` Joel Brobecker
2015-06-12 15:09 ` Martin Simmons
2015-06-12 17:58 ` Joel Brobecker
2015-06-15 10:02 ` Yao Qi
2015-06-15 13:36 ` Joel Brobecker [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=20150615133613.GE25717@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=martin@lispworks.com \
--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