From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <archer-return-1818-listarch-archer=sourceware.org@sourceware.org>
Received: (qmail 30390 invoked by alias); 17 Dec 2009 17:20:57 -0000
Mailing-List: contact archer-help@sourceware.org; run by ezmlm
Sender: <archer@sourceware.org>
Precedence: bulk
List-Post: <mailto:archer@sourceware.org>
List-Help: <mailto:archer-help@sourceware.org>
List-Subscribe: <mailto:archer-subscribe@sourceware.org>
List-Id: <archer.sourceware.org>
Received: (qmail 30376 invoked by uid 22791); 17 Dec 2009 17:20:56 -0000
X-SWARE-Spam-Status: No, hits=-1.9 required=5.0
	tests=AWL,BAYES_00,SARE_MSGID_LONG40,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: sourceware.org
MIME-Version: 1.0
In-Reply-To: <20091217165321.GA28783@caradoc.them.org>
References: <m38wda337i.fsf@fleche.redhat.com>
	 <m3skbhw1j6.fsf@fleche.redhat.com>
	 <20091211235901.GA16889@caradoc.them.org>
	 <m3fx7dqix5.fsf@fleche.redhat.com>
	 <20091214230947.GA31362@caradoc.them.org>
	 <8ac60eac0912170838r39c6916cte5a54a458a859010@mail.gmail.com>
	 <20091217165321.GA28783@caradoc.them.org>
Date: Thu, 17 Dec 2009 17:20:00 -0000
Message-ID: <8ac60eac0912170920w3a9e71ebr915bae8388248f54@mail.gmail.com>
Subject: Re: Initial psymtab replacement results
From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Tom Tromey <tromey@redhat.com>, archer@sourceware.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-System-Of-Record: true
X-SW-Source: 2009-q4/txt/msg00120.txt.bz2

On Thu, Dec 17, 2009 at 8:53 AM, Daniel Jacobowitz <drow@false.org> wrote:

> If I'm going to ship pre-cached ARM Linux files, I need them to work
> on x86-linux and x86-mingw32 at a minimum. =A0Sometimes I need them to
> work on sparc-solaris2.10 or powerpc-linux or arm-linux. =A0That's where
> I was coming from.

Thanks, I understand now.

And building the cache "on demand" or at GDB install time is not a viable
option?

We did it "on demand" -- there are usually a lot of shared libraries in
the distribution which the customer doesn't care about debugging.  E.g. if
the customer is developing some crypto app, he hardly ever debugs anything
that links against libX11, so there is no point in having libX11 take space
in the cache. Conversely, customers who debug GUIs rarely care about libssl.

Building "on demand" also handles updates nicely: when e.g. libc.so gets
updated, next time you run GDB, it notices and rebuilds the cache (just
for that image).

--=20
Paul Pluzhnikov