From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kevin Buettner <kevinb@cygnus.com>
To: Kimball Thurston <kimball@sgrail.com>, Andrew Cagney <ac131313@cygnus.com>, gdb@sources.redhat.com
Subject: Re: gdb and dlopen
Date: Wed, 17 Oct 2001 12:58:00 -0000
Message-id: <1011017195838.ZM5524@ocotillo.lan>
References: <y3radyrjqf8.wl@paladin.sgrail.com> <20011016161525.A1241@nevyn.them.org> <y3r8zebjbz8.wl@paladin.sgrail.com> <20011016213252.A8694@nevyn.them.org> <20011016220353.A9538@nevyn.them.org> <y3r669fj7bd.wl@paladin.sgrail.com> <3BCCF83F.8010401@cygnus.com> <20011017010849.A23345@nevyn.them.org> <3BCDA6CF.3000308@cygnus.com> <20011017141550.B10927@nevyn.them.org> <y3rzo6qqe1r.wl@paladin.sgrail.com> <kimball@sgrail.com>
X-SW-Source: 2001-10/msg00181.html

On Oct 17, 12:09pm, Kimball Thurston wrote:

> Along the same lines of just trying to clean up unnecessary work, I
> was seeing 2 scans of all the open dsos for each dlopen call - it
> looks like we are getting 2 BPSTAT_WHAT_CHECK_SHLIBS events (in
> infrun.c) for each dlopen which causes us to rescan everything. Is
> there a way to distinguish these two events, and only do the scan
> once? 

I haven't looked at how hard it'd be, but it seems to me that it'd
be a good idea for gdb to note that a shlib event has happened without
immediately doing anything about it.  Then, when the target stops
for some other reason (than a shlib event), we handle all of them at
once.  This should cut down on the memory traffic greatly.

Kevin