From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31365 invoked by alias); 20 Feb 2004 19:57:43 -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 31348 invoked from network); 20 Feb 2004 19:57:43 -0000 Received: from unknown (HELO smtp6.mindspring.com) (207.69.200.110) by sources.redhat.com with SMTP; 20 Feb 2004 19:57:43 -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 1AuGm8-0004bY-00; Fri, 20 Feb 2004 14:57:28 -0500 Received: by berman.michael-chastain.com (Postfix, from userid 502) id D195E4B104; Fri, 20 Feb 2004 14:57:22 -0500 (EST) To: cagney@gnu.org, drow@false.org Subject: Re: Huge slowdown since 6.0 Cc: carlton@kealia.com, ezannoni@redhat.com, gdb@sources.redhat.com Message-Id: <20040220195722.D195E4B104@berman.michael-chastain.com> Date: Fri, 20 Feb 2004 19:57:00 -0000 From: mec.gnu@mindspring.com (Michael Elizabeth Chastain) X-SW-Source: 2004-02/txt/msg00296.txt.bz2 ac> It's been suggested to me that we should create a hacked gdb that ac> records all commands et.al. to a file, and then offers to send them to ac> us. That way we know what is, rather than what might be. I think we can do this just with doco. In the doco that says how to report bugs, add some basic instructions on the "script" command. Michael C