From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29613 invoked by alias); 1 Nov 2002 03:51:53 -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 29604 invoked from network); 1 Nov 2002 03:51:52 -0000 Received: from unknown (HELO crack.them.org) (65.125.64.184) by sources.redhat.com with SMTP; 1 Nov 2002 03:51:52 -0000 Received: from nevyn.them.org ([66.93.61.169] ident=mail) by crack.them.org with asmtp (Exim 3.12 #1 (Debian)) id 187Tlx-0002kJ-00; Thu, 31 Oct 2002 22:51:05 -0600 Received: from drow by nevyn.them.org with local (Exim 3.36 #1 (Debian)) id 187Sr5-0003oc-00; Thu, 31 Oct 2002 22:52:19 -0500 Date: Thu, 31 Oct 2002 19:51:00 -0000 From: Daniel Jacobowitz To: wim delvaux Cc: gdb@sources.redhat.com Subject: Re: why is gdb 5.2 so slow Message-ID: <20021101035218.GA14509@nevyn.them.org> Mail-Followup-To: wim delvaux , gdb@sources.redhat.com References: <20021101013219.QDL1261.amsfep12-int.chello.nl@there> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20021101013219.QDL1261.amsfep12-int.chello.nl@there> User-Agent: Mutt/1.5.1i X-SW-Source: 2002-10/txt/msg00226.txt.bz2 On Fri, Nov 01, 2002 at 02:32:19AM +0100, wim delvaux wrote: > I have been working with gdb 4.xx for years. > > because of the dynamic library breakpoint handing I moved to 5.2 only to find > it VERY slow. I wrote this mail because I just had to kill gdb because it > consumed 100 % cpu for MINUTES without doing anything usefull. > > I run debian (testing version with the latests versions) I have currently > installed 5.2.cvs 2002081. > > Kernel version 2.4.18 > > I must admin that I do not have the fastest workhorse imaginable (a PIII 800) > but that used to be no problem. > > I also sometimes use ddd 3.1 with gdb and again in the 4-version I had no > problem, executing was crips, debugging (almost) fun. > > Now it skips breakpoints, takes ages to skip to the next statement, sometimes > does not even want to stop (because it refers to some missing thread or > something). Only killing is the solution. > > PLEASE help me out here !!!! We can't help you unless you give us more information, of course. What are you doing? If you're complaining about slowness, you're probably working with multithreaded applications. Yeah, it's slower, but better. Every once in a while I work on making it faster but I haven't had much success yet. It should not spin for minutes on its own. What were you telling it to do? -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer