From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8951 invoked by alias); 2 May 2004 22:12:39 -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 8944 invoked from network); 2 May 2004 22:12:39 -0000 Received: from unknown (HELO mailhost.calypto.com) (66.17.65.87) by sources.redhat.com with SMTP; 2 May 2004 22:12:39 -0000 Received: from rio (rio.calypto.com [192.168.100.120]) by mailhost.calypto.com (8.11.6/8.11.6) with ESMTP id i42MCc703639 for ; Sun, 2 May 2004 15:12:38 -0700 From: Nick Savoiu To: gdb@sources.redhat.com Subject: Improving GDB startup time with large programs Date: Sun, 02 May 2004 22:12:00 -0000 User-Agent: KMail/1.6.2 MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <200405021511.46694.savoiu@ics.uci.edu> X-SW-Source: 2004-05/txt/msg00012.txt.bz2 Hi, I have a rather large project for which I would like to improve the debugging startup time. Right now it takes GDB a good 20-30 seconds (loading symbols and such, I assume) from invoking 'run' to really executing the debugged program. Does anyone have info or a pointer to info on how to optimize this? Thanks, Nick