Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@redhat.com>
To: Chris Moller <cmoller@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Patch for PR 10728
Date: Thu, 28 Jan 2010 18:09:00 -0000	[thread overview]
Message-ID: <m3zl3y9k47.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4B6096D9.1060606@redhat.com> (Chris Moller's message of "Wed, 27 	Jan 2010 14:41:13 -0500")

>>>>> "Chris" == Chris Moller <cmoller@redhat.com> writes:

Chris> The attached stuff is a patch for PR 10728:
Chris> http://sourceware.org/bugzilla/show_bug.cgi?id=10728 "infinite loop
Chris> evaluating pointer difference w/o complete debug info"

Thanks.

Chris> The bug was in valarith.c : value_ptrdiff--if the type structs showed
Chris> size == 0, things came unstuck.  This patch fixes that by issuing a
Chris> warning and assuming size = 1.

This seems reasonable enough to me.  Maybe other maintainers would
prefer an error?  I think there are precedents either way.

Chris> Index: gdb/testsuite/gdb.cp/pr10728.exp

Chris> +     untested psmang.exp

Wrong name here, this occurs a few times.

Chris> +send_gdb "print x->y2 - x->y1\n"
Chris> +
Chris> +gdb_expect {

I think we are trying to avoid send_gdb+gdb_expect, as much as possible.
This test can comfortably be written using gdb_test, so do that.

Tom


  reply	other threads:[~2010-01-28 18:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-27 19:41 Chris Moller
2010-01-28 18:09 ` Tom Tromey [this message]
2010-01-28 18:38   ` Chris Moller
2010-01-28 20:03     ` Tom Tromey
2010-02-03 20:41       ` Chris Moller
2010-02-03 20:50         ` Tom Tromey
2010-02-02 21:57 Chris Moller
2010-02-02 23:57 ` Tom Tromey
2010-02-03  4:36   ` Chris Moller
2010-02-03 18:23     ` Tom Tromey
2010-02-03  4:52   ` Chris Moller

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=m3zl3y9k47.fsf@fleche.redhat.com \
    --to=tromey@redhat.com \
    --cc=cmoller@redhat.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