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

[Paul Pluzhnikov]

On Mon, Apr 20, 2009 at 4:48 PM, Daniel Jacobowitz <drow@false.org> wrote:
> On Mon, Apr 20, 2009 at 04:39:56PM -0700, Paul Pluzhnikov wrote:
>> > I used pstack every second until the debugging actually starts and here
>> > are all the unique #0 locations in the pstack output.
...
>> This output is bogus.
>
> I thought that too the first time I read it - but see his description
> of the output (above) again :-)

Oops. I see it now; thanks.

So most of the time (481 of 461) GDB is blocked in stat. Not a big surprize.

> Nick, it sounds to me like you're debugging something that you haven't
> got enough RAM for - is the disk I/O your swap space?

I don't (yet) see any evidence for swapping either. Do you?

Cheers,
-- 
Paul Pluzhnikov