From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14780 invoked by alias); 5 Aug 2003 05:20:38 -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 14769 invoked from network); 5 Aug 2003 05:20:36 -0000 Received: from unknown (HELO localhost.redhat.com) (24.157.166.107) by sources.redhat.com with SMTP; 5 Aug 2003 05:20:36 -0000 Received: from redhat.com (localhost [127.0.0.1]) by localhost.redhat.com (Postfix) with ESMTP id 640C52B7F; Tue, 5 Aug 2003 01:20:26 -0400 (EDT) Message-ID: <3F2F3E9A.6050403@redhat.com> Date: Tue, 05 Aug 2003 05:20:00 -0000 From: Andrew Cagney User-Agent: Mozilla/5.0 (X11; U; NetBSD macppc; en-US; rv:1.0.2) Gecko/20030223 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Vazan Cc: gdb@sources.redhat.com Subject: Re: Terminally slow (75 seconds) on some steps References: <1057999221.6815.ezmlm@sources.redhat.com> <3F16D022.30209@redhat.com> <3F186D0B.5020902@redhat.com> <3F1BF6D4.6090801@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2003-08/txt/msg00057.txt.bz2 > On Mon, 21 Jul 2003 10:21:08 -0400 Andrew Cagney wrote: > > >> So 11 seconds after you typed `run'. >> (The word startup can either be appled to that time after "run", or the >> time for gdb to reach the first "(gdb)" prompt :-(). > > > Sorry, 11 seconds after "run" command. Gdb startup takes about one > second. good (but the time is bad). >> Lots of shared libraries? Ok, during library load, GDB has to constantly start/stop the target - and that slows things down. Would you be able to oprofile your entire system so its possible to see exactly where that 11 seconds goes? A simple gprof isn't sufficient: it is the combination of GDB <-> libthread-db? <-> kernel <-> program, that slows things down. The speed improvement in moving from 5.2 -> 5.2 came from identifying a situtation where GDB was performing millions of system calls. There will likely be other cases. I suspect, because of what you'r using, GDB is loading up libthread-db and that may also add to the load. Andrew