From: Simon Marchi <simon.marchi@polymtl.ca>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA] Fix size check in dwarf2_evaluate_loc_desc_full
Date: Mon, 29 May 2017 20:55:00 -0000 [thread overview]
Message-ID: <d2ad0d78475626f998ca0a246dc48656@polymtl.ca> (raw)
In-Reply-To: <20170529162544.8652-1-tom@tromey.com>
On 2017-05-29 18:25, Tom Tromey wrote:
> This Rust bug report:
>
> https://github.com/rust-lang/rust/issues/41970
>
> noted an error from gdb. What is happening here (for me, the original
> report had a different error) is that a pieced DWARF expression is not
> writing to every byte in the resulting value. GDB errors in this
> case. However, it seems to me that it is always valid to write fewer
> bytes; the issue comes from writing too many -- that is, the test is
> reversed. The test was also checking the sub-object, but this also
> seems incorrect, as it's expected for the expression to write the
> entirety of the enclosing object. So, this patch reverses the test
> and applies it to the outer type, not the subobject type.
Your explanation sounds sensible to me (and the tests suggests it's
good). Andreas, since you played with DWARF pieces quite a bit, do you
have an opinion on this?
Would it be possible to test the error case as well by feeding bad DWARF
info in the test case?
Thanks!
Simon
next prev parent reply other threads:[~2017-05-29 20:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 16:25 Tom Tromey
2017-05-29 20:55 ` Simon Marchi [this message]
2017-05-29 23:19 ` Tom Tromey
2017-05-30 5:51 ` Simon Marchi
2017-06-27 18:23 ` Pedro Alves
2017-07-09 17:22 ` Tom Tromey
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=d2ad0d78475626f998ca0a246dc48656@polymtl.ca \
--to=simon.marchi@polymtl.ca \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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