Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Chris Moller <cmoller@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Patch for PR 9399
Date: Wed, 09 Dec 2009 14:05:00 -0000	[thread overview]
Message-ID: <20091209140534.GA12330@caradoc.them.org> (raw)
In-Reply-To: <4B1FA6F2.1060105@redhat.com>

On Wed, Dec 09, 2009 at 08:32:34AM -0500, Chris Moller wrote:
> The patch file includes the patch to gdb/valops.c, gdb/ChangeLog,
> gdb/testsuite/ChangeLog, gdb/testsuite/gdb.cp/Makefile.in, and
> mc-log.diffs.  (The patch to  Makefile.in is to incorporate the
> testcase for 'make check'; mc-log.diffs are the diffs between before
> and after runs of 'make check')

Next time, please diff -u gdb.sum files; the rest is just noise.
Those do vary a little bit but they're more stable.  It looks like
your only change is mi-nsmoribund.exp, which is sometimes flaky.

> I can't do a 'cvs add' so the the
> testcase expects and .cc file are attached separately as
> gdb/testsuite/gdb.cp/virtfunc2.cc and
> gdb/testsuite/gdb.cp/virtfunc2.exp.

Take a look at cvsutils; "cvsdo add" works.

(Or, nowadays, I suppose you could use the git mirror! :-)

> You can see what the patch does by compiling -g virtfunc.cc, gdb-ing
> it, breaking in the return stmt at // marker1, and doing things like
> "print o.do_print()".  Without the patch, gdb tries to access
> location 0x0; with the patch it does the right thing.  (There are
> more tests in virtfunc2.exp)

Where does the access to 0x0 come from?  Is it inside
search_struct_field?  I wouldn't expect value_cast_structs to do any
cast in this case, but it does do a little extra work.

> +   if ((TYPE_NAME (t1) != NULL) &&
> +       (TYPE_NAME (t2) != NULL) &&
> +       !strcmp (TYPE_NAME (t1), TYPE_NAME (t2)))

&& on the beginning of the line, please.

-- 
Daniel Jacobowitz
CodeSourcery


  reply	other threads:[~2009-12-09 14:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-09 13:32 Chris Moller
2009-12-09 14:05 ` Daniel Jacobowitz [this message]
2009-12-09 15:10   ` Chris Moller
2009-12-10 18:41     ` Daniel Jacobowitz
2009-12-10 19:04       ` Tom Tromey
2009-12-10 19:09         ` Chris Moller
2009-12-10 19:13         ` Daniel Jacobowitz
2009-12-10 16:59 ` Tom Tromey
2009-12-10 18:33   ` Chris Moller
2009-12-10 18:55     ` 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=20091209140534.GA12330@caradoc.them.org \
    --to=drow@false.org \
    --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