From: Tom Tromey <tromey@redhat.com>
To: Hui Zhu <teawater@gmail.com>
Cc: Yao Qi <yao@codesourcery.com>,
gdb-patches ml <gdb-patches@sourceware.org>,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: [PATCH] Fix agent code generate bug of ref
Date: Tue, 12 Mar 2013 14:17:00 -0000 [thread overview]
Message-ID: <87y5dsityl.fsf@fleche.redhat.com> (raw)
In-Reply-To: <CANFwon0UqJtN2O7poC8d0X+puqR-LCfw368qKJJs50YE_wexZA@mail.gmail.com> (Hui Zhu's message of "Tue, 12 Mar 2013 10:52:56 +0800")
>>>>> "Hui" == Hui Zhu <teawater@gmail.com> writes:
Hui> Sorry for my misunderstand in your mail. Accord to discussion with
Hui> Yao in IRC. I merge 2 patches together.
Hui> And I found that gdb_assert of access_memory. It should use nbytes.
Thanks for doing this.
Hui> 2013-03-12 Yao Qi <yao@codesourcery.com>
Hui> Hui Zhu <hui_zhu@mentor.com>
Hui> * dwarf2loc.c (access_memory): Change nbits to nbytes in gdb_assert.
Hui> (dwarf2_compile_expr_to_ax): Call access_memory in DW_OP_deref and
Hui> DW_OP_deref_size.
Hui> + gdb_assert (nbytes > 0 && nbytes <= sizeof (LONGEST));
Hui> - default:
Hui> - /* Note that get_DW_OP_name will never return
Hui> - NULL here. */
Hui> - error (_("Unsupported size %d in %s"),
Hui> - size, get_DW_OP_name (op));
Hui> - }
I think we need a sanity check before calling access_memory.
Otherwise, bad DWARF will be able to crash gdb.
The patch is ok with that change.
Tom
next prev parent reply other threads:[~2013-03-12 14:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-10 5:01 Hui Zhu
2013-03-11 13:39 ` Yao Qi
2013-03-11 14:38 ` Tom Tromey
2013-03-11 14:56 ` Tom Tromey
2013-03-12 2:53 ` Hui Zhu
2013-03-12 14:17 ` Tom Tromey [this message]
2013-03-12 14:48 ` Hui Zhu
2013-03-12 15:16 ` Tom Tromey
2013-03-12 15:25 ` Hui Zhu
2013-03-12 15:27 ` Tom Tromey
2013-03-12 15:47 ` Hui Zhu
2013-03-12 16:18 ` Tom Tromey
2013-03-12 2:22 ` Hui Zhu
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=87y5dsityl.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=teawater@gmail.com \
--cc=yao@codesourcery.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