Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: carlton@kealia.com, mec.gnu@mindspring.com
Cc: eliz@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [rfa/doco] PROBLEMS: add regressions since gdb 6.0
Date: Fri, 19 Mar 2004 00:09:00 -0000	[thread overview]
Message-ID: <20040317201544.575E14B104@berman.michael-chastain.com> (raw)

Yes, I too wish there was a list of PR's fixed.

I don't think it's all that helpful to the users.  As a user of *gcc*,
I look at their list of PR's fixed, and I say "yeah okay cool", and
then I run my own before+after spin anyways.  But as a tester of gdb,
I enjoy looking at my "compare by gdb" tables and seeing all the
FAIL->PASS transititions.

> Of course, it helps that GCC has several people who try to make sure
> that their bug database is as up to date as possible and organized in
> such a way as to make it easy to figure out this information.

Our bug database has several deficiencies.  It's hard to make
attachments (bugzilla is much easier).  We ask for fields that are
not important, like "severity", and do not ask for information that
is critical, like "what compiler are you using".  We need a page that
says "here is the Unix 'script' command, please attach a typescript
with your bug report".  And then there's all that nifty milestone
stuff.

> Whereas you're the only person seriously looking at the GDB bug database,
> and you're also focused (perhaps more focused) on regression testing.

Mark K and Andrew C and Daniel J and David C spend a lot of time
in there too.

Michael C


WARNING: multiple messages have this Message-ID
From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: carlton@kealia.com, mec.gnu@mindspring.com
Cc: eliz@gnu.org, gdb-patches@sources.redhat.com
Subject: Re: [rfa/doco] PROBLEMS: add regressions since gdb 6.0
Date: Wed, 17 Mar 2004 20:15:00 -0000	[thread overview]
Message-ID: <20040317201544.575E14B104@berman.michael-chastain.com> (raw)
Message-ID: <20040317201500.ScaKCeEpaqVI7DbMXjkV9ukieY5vgaE0Evm0BRSlACs@z> (raw)

Yes, I too wish there was a list of PR's fixed.

I don't think it's all that helpful to the users.  As a user of *gcc*,
I look at their list of PR's fixed, and I say "yeah okay cool", and
then I run my own before+after spin anyways.  But as a tester of gdb,
I enjoy looking at my "compare by gdb" tables and seeing all the
FAIL->PASS transititions.

> Of course, it helps that GCC has several people who try to make sure
> that their bug database is as up to date as possible and organized in
> such a way as to make it easy to figure out this information.

Our bug database has several deficiencies.  It's hard to make
attachments (bugzilla is much easier).  We ask for fields that are
not important, like "severity", and do not ask for information that
is critical, like "what compiler are you using".  We need a page that
says "here is the Unix 'script' command, please attach a typescript
with your bug report".  And then there's all that nifty milestone
stuff.

> Whereas you're the only person seriously looking at the GDB bug database,
> and you're also focused (perhaps more focused) on regression testing.

Mark K and Andrew C and Daniel J and David C spend a lot of time
in there too.

Michael C


             reply	other threads:[~2004-03-17 20:15 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-19  0:09 Michael Elizabeth Chastain [this message]
2004-03-17 20:15 ` Michael Elizabeth Chastain
2004-03-18 17:13 ` PR activity; Was: " Andrew Cagney
2004-03-19  0:09   ` Andrew Cagney
  -- strict thread matches above, loose matches on Subject: below --
2004-03-19  0:09 Michael Elizabeth Chastain
2004-03-17 18:21 ` Michael Elizabeth Chastain
2004-03-17 22:11 ` Andrew Cagney
2004-03-19  0:09   ` Andrew Cagney
2004-03-19  0:09 Michael Elizabeth Chastain
2004-03-17 19:21 ` Michael Elizabeth Chastain
2004-03-19  0:09 Michael Elizabeth Chastain
2004-03-17  6:58 ` Michael Elizabeth Chastain
2004-03-19  0:09 Michael Elizabeth Chastain
2004-03-18 16:23 ` Michael Elizabeth Chastain
2004-03-19  0:09 ` Andrew Cagney
2004-03-19  0:27   ` Daniel Jacobowitz
2004-03-19 14:56     ` Eli Zaretskii
2004-03-19 15:03     ` Andrew Cagney
2004-03-19 15:33       ` Eli Zaretskii
2004-03-19 15:54         ` Andrew Cagney
2004-03-20 15:38           ` Eli Zaretskii
2004-03-19  0:09 ` David Carlton
2004-03-18 16:45   ` David Carlton
2004-03-19  0:09 Michael Elizabeth Chastain
2004-03-17 19:30 ` Michael Elizabeth Chastain
2004-03-17 19:48 ` David Carlton
2004-03-19  0:09   ` David Carlton
2004-03-19  0:09   ` Eli Zaretskii
2004-03-18  6:06     ` Eli Zaretskii
2004-03-17 22:54 Michael Elizabeth Chastain
2004-03-17 23:39 ` Andrew Cagney
2004-03-18  6:16   ` Eli Zaretskii
2004-03-18 16:05     ` Andrew Cagney
2004-03-18 16:52       ` Eli Zaretskii
2004-03-19  0:09         ` Eli Zaretskii
2004-03-19  0:09       ` Andrew Cagney
2004-03-19  0:09     ` Eli Zaretskii
2004-03-19  0:09   ` Andrew Cagney
2004-03-19  0:09 ` Michael Elizabeth Chastain
2004-03-17 18:55 Michael Elizabeth Chastain
2004-03-17 19:03 ` David Carlton
2004-03-19  0:09   ` David Carlton
2004-03-19  0:09 ` Michael Elizabeth Chastain
2004-03-19  0:09 ` David Carlton
2004-03-17 19:16   ` David Carlton
2004-03-17  1:53 Michael Elizabeth Chastain
2004-03-17 16:13 ` Andrew Cagney
2004-03-19  0:09   ` Andrew Cagney
2004-03-17 17:05 ` David Carlton
2004-03-19  0:09   ` David Carlton
2004-03-19  0:09 ` Eli Zaretskii
2004-03-17  6:16   ` Eli Zaretskii
2004-03-19  0:09 ` Michael Elizabeth Chastain
2004-03-19  0:09 ` David Carlton
2004-03-17 17:19   ` David Carlton
2004-03-19  0:09   ` Eli Zaretskii
2004-03-17 19:07     ` Eli Zaretskii
2004-03-19  0:09     ` David Carlton
2004-03-17 19:18       ` David Carlton
2004-03-19  0:09     ` Andrew Cagney
2004-03-17 22:11       ` Andrew Cagney
2004-03-19  0:09       ` Eli Zaretskii
2004-03-18  6:11         ` Eli Zaretskii
2004-03-18 16:36         ` Daniel Jacobowitz
2004-03-19  0:09           ` Eli Zaretskii
2004-03-18 16:55             ` Eli Zaretskii
2004-03-19  0:09           ` Daniel Jacobowitz
2004-03-19  0:09           ` Andrew Cagney
2004-03-19  0:25             ` Daniel Jacobowitz

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=20040317201544.575E14B104@berman.michael-chastain.com \
    --to=mec.gnu@mindspring.com \
    --cc=carlton@kealia.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sources.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