From: mec.gnu@mindspring.com (Michael Elizabeth Chastain)
To: fnf@ninemoons.com
Cc: drow@mvista.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] - Accept optional printed address at function breakpoints
Date: Mon, 08 Dec 2003 18:02:00 -0000 [thread overview]
Message-ID: <20031208180213.A014A4B412@berman.michael-chastain.com> (raw)
Fred Fish writes:
> On one hand, I can see the value of having just a single test that
> focuses on confirming/enforcing this behavior and be more lenient
> about the patterns we accept in general. On the other hand, I can see
> that having dozens of new failures pop up due to a change in gcc debug
> output could be helpful in getting enough attention to get the problem
> fixed.
I favor the first hand. I would like to have one specific test script
which is devoted to this issue with a bunch of cases in it. Then let it
slide in every other test script.
To be sure, we might not get complete coverage of this bug without all
the windfall testing from other places. But it's just not a very
important bug to users, so I think it's not worth vitiating other parts
of the test suite just to get more coverage of this bug.
As far as the "dozens of new failures" go, it is easier for me if a bug
causes one FAIL rather than a dozen FAILs. I do track every individual
result change.
Michael C
next reply other threads:[~2003-12-08 18:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-08 18:02 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-08 16:53 Michael Elizabeth Chastain
2003-12-08 16:25 Fred Fish
2003-12-08 16:48 ` Daniel Jacobowitz
2003-12-08 17:51 ` Fred Fish
2003-12-09 4:39 ` Fred Fish
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=20031208180213.A014A4B412@berman.michael-chastain.com \
--to=mec.gnu@mindspring.com \
--cc=drow@mvista.com \
--cc=fnf@ninemoons.com \
--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