From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8931 invoked by alias); 27 Mar 2003 22:23:23 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 8923 invoked from network); 27 Mar 2003 22:23:22 -0000 Received: from unknown (HELO localhost.redhat.com) (207.219.125.105) by sources.redhat.com with SMTP; 27 Mar 2003 22:23:22 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 820002B23; Thu, 27 Mar 2003 17:23:21 -0500 (EST) Message-ID: <3E8379D9.3060508@redhat.com> Date: Thu, 27 Mar 2003 22:23:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Daniel Jacobowitz Cc: gdb@sources.redhat.com, Jim Blandy Subject: Re: [Fwd: Re: tdep/1155: s/390 Linux: GDB can't reselect the right frame after an inferior function call] References: <3E836DFA.2070603@redhat.com> <20030327213715.GA19131@nevyn.them.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-03/txt/msg00380.txt.bz2 > 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