From: Andrew Cagney <ac131313@ges.redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: Fernando Nasser <fnasser@redhat.com>,
Michael Elizabeth Chastain <mec@shout.net>,
gdb@sources.redhat.com, carlton@math.stanford.edu
Subject: Re: Pinging Michael C
Date: Mon, 16 Sep 2002 12:05:00 -0000 [thread overview]
Message-ID: <3D862B87.3020704@ges.redhat.com> (raw)
In-Reply-To: <20020916150921.GA9184@nevyn.them.org>
>> 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...
>
>
> Fortunately, David has since fixed the bug. I think this patch is
> ready to go in, once we agree on ChangeLog formatting.
>
>
>> > 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...
>
>
> I have an even better idea (I think :). I'll post an RFC for it in a
> second.
Fernando and I were discussing the idea of:
gdb.base/gdb-bugs.exp (gdb.base/base-bugs.exp?)
gdb.mi/mi-bugs.exp
(just waiting :-)
Andrew
next prev parent reply other threads:[~2002-09-16 19:05 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
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 [this message]
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=3D862B87.3020704@ges.redhat.com \
--to=ac131313@ges.redhat.com \
--cc=carlton@math.stanford.edu \
--cc=drow@mvista.com \
--cc=fnasser@redhat.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