Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@redhat.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Make SIZE element for dwarf_block as size_t
Date: Mon, 23 Jul 2012 17:29:00 -0000	[thread overview]
Message-ID: <20120723225922.30d293e7@spoyarek> (raw)
In-Reply-To: <87fw8isfoo.fsf@fleche.redhat.com>

On Mon, 23 Jul 2012 08:41:27 -0600, Tom wrote:
> What about dwarf2_evaluate_loc_desc_full?
> It has 'unsigned short size' as an argument but is called from
> indirect_pieced_value:
> 
>   struct dwarf2_locexpr_baton baton;
> [...]
>   return dwarf2_evaluate_loc_desc_full (TYPE_TARGET_TYPE (type),
> frame, baton.data, baton.size, baton.per_cu,
> 					piece->v.ptr.offset +
> byte_offset);

Ah yes, I missed that, thanks. I'll look through once more.

> It would have been useful to me if you had written a bit about how you
> wrote this patch and verified it.  As it is, with no information on
> that, I went grepping through the source to see if the patch was
> complete.

The fix was partly ripped out of the bitpos-expand patch[1] that I am
working on, in am attempt to make that patch a little smaller (not that
I've succeeded much at all). My current method for verification is just
to ensure that there are no regressions in the testsuite and grepping
through the code to try and ensure that I haven't missed anything
(which I did this time). I don't have a reproducer that demonstrates any
breakage due to this, but I can try to come up with one if it is
necessary.

Regards,
Siddhesh

[1] http://sourceware.org/ml/gdb-patches/2012-06/msg00851.html


  reply	other threads:[~2012-07-23 17:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-22  7:47 Siddhesh Poyarekar
2012-07-22  8:28 ` Siddhesh Poyarekar
2012-07-23 14:41   ` Tom Tromey
2012-07-23 17:29     ` Siddhesh Poyarekar [this message]
2012-07-23 18:53       ` Tom Tromey
2012-07-25 17:21         ` [PATCH][v2] " Siddhesh Poyarekar
2012-07-25 17:58           ` 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=20120723225922.30d293e7@spoyarek \
    --to=siddhesh@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tromey@redhat.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