From: Andrew Cagney <ac131313@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>
Cc: gdb@sources.redhat.com, Jim Blandy <jimb@redhat.com>
Subject: Re: [Fwd: Re: tdep/1155: s/390 Linux: GDB can't reselect the right frame after an inferior function call]
Date: Thu, 27 Mar 2003 22:23:00 -0000 [thread overview]
Message-ID: <3E8379D9.3060508@redhat.com> (raw)
In-Reply-To: <20030327213715.GA19131@nevyn.them.org>
> On Thu, Mar 27, 2003 at 04:32:42PM -0500, Andrew Cagney wrote:
>
>> There are two ways of handling bugs:
>>
>> a. the bug remains open until every last possible [un]related issue is
>> resolved
>>
>> b. the original bug, as filed, is closed, as soon as the original
>> problem is resolved. If additional problems or enhancements are
>> identified, they are recorded in new separate bug reports
FYI, I moved this thread here because the bug database is not the place
to hold meta discussions about things like the above.
To me, as soon as the original problem is resolved, the bug should be
closed. If, as part of that analysis, new problems are found, or other
related changes are identified, then they should be tracked separatly as
new bugs.
If this isn't done, the bug database quickly accumulates misleading and
poorly filed bug reports :-(
Of course, if the original problem, as filed, turns out to not be fixed,
the bug gets re-opened (I've already re-opened the bug in question, I
misread the analysis and the original problem was not resolved :-( )
Andrew
next prev parent reply other threads:[~2003-03-27 22:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-27 21:32 Andrew Cagney
2003-03-27 21:37 ` Daniel Jacobowitz
2003-03-27 22:23 ` Andrew Cagney [this message]
2003-03-30 16:57 ` Andrew Cagney
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=3E8379D9.3060508@redhat.com \
--to=ac131313@redhat.com \
--cc=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).