From: Daniel Berlin <dberlin@dberlin.org>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [rfa:symtab] Delete broken "memory mapped objfile cache"
Date: Tue, 04 Nov 2003 17:39:00 -0000 [thread overview]
Message-ID: <D8F7FE48-0EED-11D8-A3F9-000A95AF1FAE@dberlin.org> (raw)
In-Reply-To: <3FA7D202.2050205@redhat.com>
On Nov 4, 2003, at 11:21 AM, Andrew Cagney wrote:
> Hello,
>
> (more, somewhat perverse bcache fallout)
>
> The "memory mapped objfile cache" (for want of a better name) is a
> technique where by GDB creates per-objfile disk backed memory mapped
> caches that contain the object files symbol information. Its based on
> the theory that, after each rebuild little is changed, and hence most
> symbol information can be drawn from an on-disk cache, and re-read
> from the object file. The lit, it turns out, supports the theory. A
> typical debugging rebuild changes little in an executable.
>
> So why delete it? As far as I can tell:
>
> - it hasn't worked in >4years
> - it hasn't built in >1year
> - it isn't tested
>
> I've nothing personal against the the technique. In fact I'd like to
> see a robust implementation backed by test cases and supporting
> performance data. However, I strongly object to GDB having to carry
> around long-ago broken code. By deleting this, we clear the decks for
> a modern robust implementation (the original code appears to date back
> to '92).
Actually, apple has it implemented and working.
Maybe they'd like to share?
If so, and they need that code, maybe we should keep it around for just
a bit longer.
next prev parent reply other threads:[~2003-11-04 17:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-04 16:21 Andrew Cagney
2003-11-04 17:39 ` Daniel Berlin [this message]
2003-11-04 18:15 ` Andrew Cagney
2003-11-05 6:24 ` Eli Zaretskii
2003-11-17 18:36 ` Andrew Cagney
2003-11-17 18:39 ` Daniel Jacobowitz
2004-01-19 16:51 ` Elena Zannoni
2004-01-19 19:56 ` Andrew Cagney
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=D8F7FE48-0EED-11D8-A3F9-000A95AF1FAE@dberlin.org \
--to=dberlin@dberlin.org \
--cc=ac131313@redhat.com \
--cc=gdb-patches@sources.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