From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25884 invoked by alias); 21 Apr 2009 15:51:58 -0000 Received: (qmail 25848 invoked by uid 22791); 21 Apr 2009 15:51:56 -0000 X-SWARE-Spam-Status: No, hits=-2.5 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from sibelius.xs4all.nl (HELO sibelius.xs4all.nl) (82.92.89.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 21 Apr 2009 15:51:49 +0000 Received: from brahms.sibelius.xs4all.nl (kettenis@localhost.sibelius.xs4all.nl [127.0.0.1]) by brahms.sibelius.xs4all.nl (8.14.3/8.14.3) with ESMTP id n3LFpiOZ026823; Tue, 21 Apr 2009 17:51:44 +0200 (CEST) Received: (from kettenis@localhost) by brahms.sibelius.xs4all.nl (8.14.3/8.14.3/Submit) id n3LFphaO009791; Tue, 21 Apr 2009 17:51:43 +0200 (CEST) Date: Tue, 21 Apr 2009 15:52:00 -0000 Message-Id: <200904211551.n3LFphaO009791@brahms.sibelius.xs4all.nl> From: Mark Kettenis To: savoiu@yahoo.com CC: gdb@sourceware.org In-reply-to: <742711.93110.qm@web52008.mail.re2.yahoo.com> (message from Nick Savoiu on Mon, 20 Apr 2009 17:17:46 -0700 (PDT)) Subject: Re: GDB using a lot of CPU time and writing a lot to disk on startup References: <592922.54823.qm@web52001.mail.re2.yahoo.com> <8ac60eac0904201639r19f7d539v2b301fcb24e82317@mail.gmail.com> <20090420234805.GA28850@caradoc.them.org> <8ac60eac0904201654h1775560se59718b127ccbfad@mail.gmail.com> <742711.93110.qm@web52008.mail.re2.yahoo.com> Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2009-04/txt/msg00172.txt.bz2 > Date: Mon, 20 Apr 2009 17:17:46 -0700 (PDT) > From: Nick Savoiu > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 2381 nsavoiu 15 0 594m 424m 34m S 0 10.9 0:49.13 kdevelop > 2381 nsavoiu 16 0 594m 424m 34m S 1 10.9 0:49.31 kdevelop > > 7810 nsavoiu 16 0 140m 130m 2472 S 22 3.4 0:03.92 gdb > 7810 nsavoiu 16 0 634m 622m 2536 S 73 16.0 1:51.12 gdb Heh, if memory consumption is to blame, kdevelop is about as guilty as gdb ;) > 7816 nsavoiu 25 0 153m 138m 61m T 0 3.6 0:08.23 kernel > 7816 nsavoiu 25 0 153m 138m 61m T 0 3.6 0:08.23 kernel > > so my best guess was GDB given where the CPU times went. No other processes were running actively and there was enough memory > > Mem: 3975148k total, 3372012k used, 603136k free, 86136k buffers > Swap: 8385848k total, 756112k used, 7629736k free, 1407932k cached > > so swapping should not be an issue. Well, your system *is* using swap. Are you running Linux? I wouldn't be surprised if it is swapping out kdevelop because gdb is the active application and is reading in a lot of debugging info.