Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Paul Koning <paulkoning@comcast.net>
To: pmuldoon@redhat.com
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
Subject: Re: Python: fetch value when building gdb.Value object [rediff]
Date: Mon, 03 Oct 2011 16:16:00 -0000	[thread overview]
Message-ID: <25071E96-2ACB-4ED0-83CE-BE3B7187BB31@comcast.net> (raw)
In-Reply-To: <m3y5x2gyym.fsf@redhat.com>


On Oct 3, 2011, at 6:18 AM, Phil Muldoon wrote:

> Jan Kratochvil <jan.kratochvil@redhat.com> writes:
> 
>> Updated for current HEAD:
>> 
>> On Sat, 01 Oct 2011 11:28:52 +0200, Jan Kratochvil wrote:
>> On Wed, 28 Sep 2011 21:24:45 +0200, Phil Muldoon wrote:
>>> What scenario will this test catch that the previous test won't?  I'm
>>> not saying you are incorrect, I just don't understand. What
>>> error-trigger does the assignment to "inval" trigger?
>> 
>> I would prefer here a testcase more clearly showing the bug, attached below.
>> 
>> I believe the patch is right, as Phil hasn't yet agreed posting it only.
> 
> It looks great, thanks for doing this.

Thanks all.

Committed.

	paul



  reply	other threads:[~2011-10-03 16:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-21 16:17 Python: fetch value when building gdb.Value object Paul Koning
2011-09-28 19:29 ` Phil Muldoon
2011-09-28 20:06   ` Paul Koning
2011-10-04 15:43     ` Tom Tromey
2011-09-28 20:42   ` Paul Koning
2011-10-01  9:05     ` Jan Kratochvil
2011-10-03 10:22       ` Phil Muldoon
2011-10-04 15:40       ` Tom Tromey
2011-10-01  9:29   ` Jan Kratochvil
2011-10-01 10:23     ` Pedro Alves
2011-10-01 11:03       ` Jan Kratochvil
2011-10-01 12:17     ` Python: fetch value when building gdb.Value object [rediff] Jan Kratochvil
2011-10-01 18:58       ` Paul Koning
2011-10-03 10:19       ` Phil Muldoon
2011-10-03 16:16         ` Paul Koning [this message]
2011-10-01  1:00 ` [PING] [RFA] Re: Python: fetch value when building gdb.Value object Paul Koning
2011-10-04 15:45 ` Tom Tromey
2011-10-04 15:51   ` Paul Koning
2011-10-14 20:03     ` Tom Tromey
2011-10-14 20:30       ` Paul Koning
2011-10-19 20:56         ` Tom Tromey
2011-10-19 20:58           ` Paul Koning
2011-10-20 15:09             ` Tom Tromey
2011-10-21  7:46               ` Paul Koning
2011-10-21 17:13                 ` Tom Tromey
2011-10-14 23:36   ` Jim Blandy

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=25071E96-2ACB-4ED0-83CE-BE3B7187BB31@comcast.net \
    --to=paulkoning@comcast.net \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=pmuldoon@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