This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: [Fwd: Re: tdep/1155: s/390 Linux: GDB can't reselect the rightframe after an inferior function call]
- From: Andrew Cagney <ac131313 at redhat dot com>
- To: Daniel Jacobowitz <drow at mvista dot com>
- Cc: gdb at sources dot redhat dot com, Jim Blandy <jimb at redhat dot com>
- Date: Thu, 27 Mar 2003 17:23:21 -0500
- Subject: Re: [Fwd: Re: tdep/1155: s/390 Linux: GDB can't reselect the rightframe after an inferior function call]
- References: <3E836DFA.2070603@redhat.com> <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