From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30195 invoked by alias); 1 Nov 2002 01:32:21 -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 30133 invoked from network); 1 Nov 2002 01:32:20 -0000 Received: from unknown (HELO amsfep12-int.chello.nl) (213.46.243.18) by sources.redhat.com with SMTP; 1 Nov 2002 01:32:20 -0000 Received: from there ([62.205.65.176]) by amsfep12-int.chello.nl (InterMail vM.5.01.03.06 201-253-122-118-106-20010523) with SMTP id <20021101013219.QDL1261.amsfep12-int.chello.nl@there> for ; Fri, 1 Nov 2002 02:32:19 +0100 Content-Type: text/plain; charset="iso-8859-1" From: wim delvaux To: gdb@sources.redhat.com Subject: why is gdb 5.2 so slow Date: Thu, 31 Oct 2002 17:32:00 -0000 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20021101013219.QDL1261.amsfep12-int.chello.nl@there> X-SW-Source: 2002-10/txt/msg00225.txt.bz2 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 !!!! W