Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Michael Elizabeth Chastain <mec@shout.net>,
	gdb@sources.redhat.com, Andrew Cagney <ac131313@ges.redhat.com>,
	carlton@math.stanford.edu
Subject: Re: Pinging Michael C
Date: Mon, 16 Sep 2002 07:57:00 -0000	[thread overview]
Message-ID: <3D85F0F3.5060108@redhat.com> (raw)
In-Reply-To: <20020914045436.GA22119@nevyn.them.org>

I am assuming you all have looked at the C++ side of these tests...

Daniel Jacobowitz wrote:
> Michael,
> 
> Are you still around and at this address?  I haven't heard from you in some
> time, and David Carlton's C++ testsuite patches from August are still
> awaiting review:
>   http://sources.redhat.com/ml/gdb-patches/2002-08/msg00695.html

I wonder if next will relly be more reliable.  Anyway, we can try -- the 
test is not about breakpoints.

The following ChangeLog entries need some more info though:

	* gdb.c++/m-static.cc: Add test 4.
	* gdb.c++/m-static.h: New file.
	* gdb.c++/m-static1.cc: New file.


>   http://sources.redhat.com/ml/gdb-patches/2002-08/msg00472.html

I don't think we want to add tests to make gdb dump core to the 
testsuite right away.  It should go in as soon as someone fixes the 
problem to prevent a regression.  Alternatively we can add it in and 
explicitly skip the test with a explicit call to the kfail proc...

I don't see anything wrong with the test file itself, but the ChangeLog 
also needs some more info (what the new files do/test).

	* gdb.c++/printmethod.exp: New file.
	* gdb.c++/printmethod.cc: New file.


>   http://sources.redhat.com/ml/gdb-patches/2002-08/msg00469.html
> 

I was talking to Andrew about collecting these regression tests into a 
single file (someone would eventually move them into one of the other 
files if the test can be associated with some feature).

Andrew, what was the name of the file? I forgot...

Again, the test s OK but the ChangeLog entries need more info.
P.S.: If this is not fixed yet please use setup_kfail and refer to 
appropriate Gnats bug report.



> As is one of Jim Blandy's:
>   http://sources.redhat.com/ml/gdb-patches/2002-08/msg00670.html

Nice!  Just needs a correct ChangeLog entry in the proper format and at 
least mentioning what the new tests are for (although one could guess 
from the file names, but we don't usually rely on that).


Regards to all,
Fernando

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9


  reply	other threads:[~2002-09-16 14:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-13 21:54 Daniel Jacobowitz
2002-09-16  7:57 ` Fernando Nasser [this message]
2002-09-16  8:09   ` Daniel Jacobowitz
2002-09-16  8:54     ` Fernando Nasser
2002-09-16 10:03     ` David Carlton
2002-09-16 10:12       ` Daniel Jacobowitz
2002-09-16 10:14         ` David Carlton
2002-09-18 11:52         ` David Carlton
2002-09-16 12:05     ` Andrew Cagney
2002-09-14 11:20 Michael Elizabeth Chastain

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=3D85F0F3.5060108@redhat.com \
    --to=fnasser@redhat.com \
    --cc=ac131313@ges.redhat.com \
    --cc=carlton@math.stanford.edu \
    --cc=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=mec@shout.net \
    /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