From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23510 invoked by alias); 12 Jul 2003 09:03:58 -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 23502 invoked from network); 12 Jul 2003 09:03:57 -0000 Received: from unknown (HELO ns2.dialtelecom.sk) (81.0.192.3) by sources.redhat.com with SMTP; 12 Jul 2003 09:03:57 -0000 Received: (qmail 15488 invoked from network); 12 Jul 2003 09:03:53 -0000 Received: from unknown (HELO pcw2k69.energoinfo.sk) (81.0.194.199) by ns2.dialtelecom.sk with SMTP; 12 Jul 2003 09:03:53 -0000 Received: from main by pcw2k69.energoinfo.sk with local (MasqMail 0.1.16) id 19bGI2-4M6-00 for gdb@sources.redhat.com; Sat, 12 Jul 2003 11:03:34 +0200 Date: Sat, 12 Jul 2003 09:03:00 -0000 Subject: Terminally slow (75 seconds) on some steps To: gdb@sources.redhat.com Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Disposition: INLINE References: <1057999221.6815.ezmlm@sources.redhat.com> In-Reply-To: <1057999221.6815.ezmlm@sources.redhat.com> From: Robert Vazan X-Delivery-Agent: TMDA/0.51 (Python 2.1.3 on Linux/i686) X-SW-Source: 2003-07/txt/msg00155.txt.bz2 I am trying to debug large program and I am observing unusual slowdown. I don't have any breakpoints, I am just running the app. I measured 75 seconds of wall clock for single click operation that takes fraction of second outside debugger. Process time (as viewed by ps) of gdb increased by 68 seconds. I get realtime reaction with some operations and this delay with some other operations. When single stepping, it seems that the more lines must be executed the more time it takes in debugger (but this is in 1-5 seconds range). As if gdb was emulating every instruction. I know this isn't the case. However, breakpoints cause interrupts, so maybe gdb is being bogged down by some other interrupts, timer maybe? Given that single step can take one or more seconds, few timers could quickly accumulate to minute. I have also this problem that I cannot run the program twice per session, so I have to restart gdb and consequently reload symbols. I have aging snapshot from 1. April 2002.