From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7281 invoked by alias); 22 Jul 2004 09:35:33 -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 7259 invoked from network); 22 Jul 2004 09:35:32 -0000 Received: from unknown (HELO smtp6.mindspring.com) (207.69.200.110) by sourceware.org with SMTP; 22 Jul 2004 09:35:32 -0000 Received: from user-119a90a.biz.mindspring.com ([66.149.36.10] helo=berman.michael-chastain.com) by smtp6.mindspring.com with esmtp (Exim 3.33 #1) id 1BnZz5-0003qd-00; Thu, 22 Jul 2004 05:35:27 -0400 Received: by berman.michael-chastain.com (Postfix, from userid 502) id 624FF4B104; Thu, 22 Jul 2004 05:35:53 -0400 (EDT) To: eliz@gnu.org, kettenis@chello.nl Subject: Re: [6.2] PROBLEMS file Cc: cagney@gnu.org, gdb@sources.redhat.com Message-Id: <20040722093553.624FF4B104@berman.michael-chastain.com> Date: Thu, 22 Jul 2004 12:14:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-07/txt/msg00279.txt.bz2 Mark Kettenis writes: > There will always be cases where GDB will get confused and lose track. > In that case it will possibly provide an endless or very long backtrace > containing garbage. I'm okay with this part, as long as the user can easily get it out of it at the "press space to continue" prompt. It would be nice to have an adjustable cutoff defaulting to perhaps 1000 or 10,000 frames. I've had some huge gdb.log files (20 megabytes) because the test suite triggered such a bug and then gdb wouldn't quit. > So IMHO there is no regression here. PR 1505 should be closed. It's a regression if a specific sequence of commands works with gdb N and does not work with gdb N+1. You might have to say "can't fix" or "won't fix". Michael C