From: Yao Qi <qiyaoltc@gmail.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] PR 19947: throw right exception in read_code and read_stack
Date: Tue, 19 Apr 2016 07:50:00 -0000 [thread overview]
Message-ID: <1461052220-10149-1-git-send-email-yao.qi@linaro.org> (raw)
Hi,
Patch 1 triggers PR 19947, because it uses -fno-asynchronous-unwind-tables
in the compilation of test case, so that there is no DWARF info, and GDB
has to choose prologue unwinder. In this way, the prologue unwinder can
be tested under the situation that memory/register is not available.
Patch 2 is the fix, by throwing the right exception in read_code and
read_stack. See details in patch 2.
Regression tested on x86_64-linux.
*** BLURB HERE ***
Yao Qi (2):
Use -fno-asynchronous-unwind-tables if C program is compiled without
debug info on x86
Throw NOT_AVAILABLE_ERROR in read_stack and read_code
gdb/corefile.c | 29 +++++++++++++++--------------
gdb/testsuite/lib/gdb.exp | 9 +++++++++
2 files changed, 24 insertions(+), 14 deletions(-)
--
1.9.1
next reply other threads:[~2016-04-19 7:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 7:50 Yao Qi [this message]
2016-04-19 7:50 ` [PATCH 1/2] Use -fno-asynchronous-unwind-tables if C program is compiled without debug info on x86 Yao Qi
2016-04-19 13:35 ` Pedro Alves
2016-04-20 8:38 ` Yao Qi
2016-04-22 12:30 ` Pedro Alves
2016-04-22 14:23 ` Yao Qi
2016-04-22 14:36 ` Pedro Alves
2016-04-22 16:05 ` Yao Qi
2016-04-19 7:50 ` [PATCH 2/2] Throw NOT_AVAILABLE_ERROR in read_stack and read_code Yao Qi
2016-04-22 13:41 ` Pedro Alves
2016-05-04 14:08 ` Yao Qi
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=1461052220-10149-1-git-send-email-yao.qi@linaro.org \
--to=qiyaoltc@gmail.com \
--cc=gdb-patches@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).