From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23404 invoked by alias); 18 Mar 2004 19:34:25 -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 23392 invoked from network); 18 Mar 2004 19:34:24 -0000 Received: from unknown (HELO nevyn.them.org) (66.93.172.17) by sources.redhat.com with SMTP; 18 Mar 2004 19:34:24 -0000 Received: from drow by nevyn.them.org with local (Exim 4.30 #1 (Debian)) id 1B43Hb-0006bB-GW; Thu, 18 Mar 2004 14:34:23 -0500 Date: Thu, 18 Mar 2004 19:34:00 -0000 From: Daniel Jacobowitz To: Nick Savoiu Cc: gdb@sources.redhat.com Subject: Re: Caching of object/libraries/files Message-ID: <20040318193423.GA25318@nevyn.them.org> Mail-Followup-To: Nick Savoiu , gdb@sources.redhat.com References: <04b201c40d19$602c8390$a60bc380@ics.uci.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <04b201c40d19$602c8390$a60bc380@ics.uci.edu> User-Agent: Mutt/1.5.1i X-SW-Source: 2004-03/txt/msg00174.txt.bz2 On Thu, Mar 18, 2004 at 10:46:47AM -0800, Nick Savoiu wrote: > Hi all, > > I have a rather large project composed of a small driver executable and > quite a few .so libraries that it uses. > > When I invoke it with GDB, upon executing 'run' it takes quite a while for > GDB to do it's thing (i.e. load symbols, whatever else it does) particularly > since it does a lot of disk access. > > I was thinking that, if I start a GDB session on this project, run it for a > while then quit and immediately restart a similar session, then most of the > files would be cached. However, I see the same amount of disk access for the > second session when 'run' is invoked as for the first. > > Any ideas why this is so? The GDB session itself uses about 340MB and I have > 1GB RAM. This is something that I've been meaning to fix for a long, long time. We unload all shared objects when the program exits; what we ought to do is move them to a separate cache structure. -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer