This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: GDB using a lot of CPU time and writing a lot to disk on startup


> Date: Mon, 20 Apr 2009 17:17:46 -0700 (PDT)
> From: Nick Savoiu <savoiu@yahoo.com>
> 
>   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.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]