public inbox for archer@sourceware.org
 help / color / mirror / Atom feed
From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Tom Tromey <tromey@redhat.com>, archer@sourceware.org
Subject: Re: Initial psymtab replacement results
Date: Thu, 17 Dec 2009 17:20:00 -0000	[thread overview]
Message-ID: <8ac60eac0912170920w3a9e71ebr915bae8388248f54@mail.gmail.com> (raw)
In-Reply-To: <20091217165321.GA28783@caradoc.them.org>

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.  Sometimes I need them to
> work on sparc-solaris2.10 or powerpc-linux or arm-linux.  That'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).

-- 
Paul Pluzhnikov

  reply	other threads:[~2009-12-17 17:20 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-10 21:54 Tom Tromey
2009-12-11 23:10 ` Tom Tromey
2009-12-11 23:59   ` Daniel Jacobowitz
2009-12-14 22:40     ` Tom Tromey
2009-12-14 23:09       ` Daniel Jacobowitz
2009-12-15 23:39         ` Tom Tromey
2009-12-16  3:01           ` Roland McGrath
2009-12-16 18:20             ` Tom Tromey
2009-12-16 18:57               ` Roland McGrath
2009-12-16 19:46                 ` Tom Tromey
2009-12-16 19:52                   ` Roland McGrath
2009-12-16 18:11           ` Daniel Jacobowitz
2009-12-16 19:31             ` Tom Tromey
2009-12-23 18:29           ` Tom Tromey
2009-12-23 18:35             ` Daniel Jacobowitz
2009-12-24 17:07             ` Tom Tromey
2010-01-06 23:05               ` Tom Tromey
2009-12-17 16:39         ` Paul Pluzhnikov
2009-12-17 16:53           ` Daniel Jacobowitz
2009-12-17 17:20             ` Paul Pluzhnikov [this message]
2009-12-17 18:16               ` Daniel Jacobowitz
2009-12-18 23:58                 ` Tom Tromey
2009-12-21 13:54                   ` Daniel Jacobowitz
2009-12-21 21:29                     ` Tom Tromey
2009-12-15  1:04       ` Roland McGrath
2009-12-15 18:36         ` Tom Tromey

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8ac60eac0912170920w3a9e71ebr915bae8388248f54@mail.gmail.com \
    --to=ppluzhnikov@google.com \
    --cc=archer@sourceware.org \
    --cc=drow@false.org \
    --cc=tromey@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).