From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19312 invoked by alias); 7 Aug 2004 07:26:47 -0000 Mailing-List: contact gdb-patches-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sources.redhat.com Received: (qmail 19292 invoked from network); 7 Aug 2004 07:26:44 -0000 Received: from unknown (HELO smtp10.atl.mindspring.net) (207.69.200.246) by sourceware.org with SMTP; 7 Aug 2004 07:26:44 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by smtp10.atl.mindspring.net with esmtp (Exim 3.33 #1) id 1BtLbE-0002xi-00; Sat, 07 Aug 2004 03:26:41 -0400 Received: from mindspring.com (localhost [127.0.0.1]) by berman.michael-chastain.com (Postfix) with SMTP id E33644B102; Sat, 7 Aug 2004 03:26:40 -0400 (EDT) Date: Sat, 07 Aug 2004 07:26:00 -0000 From: Michael Chastain To: drow@false.org Subject: Re: [rfa/doco] PROBLEMS: remove pr gdb/1505 Cc: gdb-patches@sources.redhat.com, eliz@gnu.org Message-ID: <4114842F.nailOJU11P7U6@mindspring.com> References: <41145FDE.nail9GZ1WMY09@mindspring.com> <20040807051342.GA15773@nevyn.them.org> In-Reply-To: <20040807051342.GA15773@nevyn.them.org> User-Agent: nail 10.8 6/28/04 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-SW-Source: 2004-08/txt/msg00195.txt.bz2 Daniel Jacobowitz wrote: drow> I'm curious - why do you believe that PR 1505 has been fixed? drow> Some particular instance may have been, but the problem definitely drow> remains - see discussion on gdb@ this week. My test bed says that the problem no longer occurs in the environment where it was reported. Something changed in gdb since the last spin and gdb finds the right bottom-of-stack now. The problem hasn't occured in any other environments that anyone has seen, either. So I closed the PR. (I optimized away the feedback step because I was the original submitter). I would tell the original submitter: if it happens again, with the same or different platform, file a new PR. I'm open to alternatives. How do you suggest we handle PR/1505? Michael C