Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@red-bean.com>
To: Eirik Fuller <eirik@hackrat.com>
Cc: David Anderson <davea@quasar.engr.sgi.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Use mmap for symbol tables
Date: Tue, 31 Jan 2006 05:34:00 -0000	[thread overview]
Message-ID: <8f2776cb0601302134w35cf9ae2v3cf03a4113fb3018@mail.gmail.com> (raw)
In-Reply-To: <43DEEEF2.7030202@hackrat.com>

On 1/30/06, Eirik Fuller <eirik@hackrat.com> wrote:
> This suggests a simple way to complicate my mmap patch.  If it can be
> determined beforehand what interval of the symbol table gdb is going to
> read in its entirety, that interval can be recorded in the BFD struct,
> and the first mmap call can map just that interval.  That will
> complicate the offset calculations somewhat, but the basic approach will
> be the same.  This will only waste virtual address space if the sections
> gdb would otherwise read don't form a contiguous region of the file.

Actually, that's a pretty great idea.  We could have the linker
arrange to put all the debug sections together; that's easy.  Then we
could have the BFD API let GDB specify a list of sections to map.  BFD
would map the smallest contiguous region containing those sections. 
You'd get an interface that works with all files, but performs better
when the linker does its job right.


  reply	other threads:[~2006-01-31  5:34 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-31  4:40 David Anderson
2006-01-31  5:00 ` Eirik Fuller
2006-01-31  5:34   ` Jim Blandy [this message]
2006-01-31 14:00     ` Daniel Jacobowitz
2006-01-31 18:39       ` Jim Blandy
2006-02-01 18:11         ` Eirik Fuller
2006-01-31 17:45 ` David Anderson
2006-01-31 18:24 ` Jim Blandy
  -- strict thread matches above, loose matches on Subject: below --
2006-01-31  4:53 David Anderson
2006-01-29 23:36 Eirik Fuller
2006-01-30  5:04 ` Jim Blandy
2006-01-30 11:44   ` Eirik Fuller
2006-01-30 18:07     ` Jim Blandy
2006-01-30 18:59       ` Eirik Fuller
2006-01-30 22:11         ` Jim Blandy
2006-01-31  0:38           ` Eirik Fuller
2006-01-31  1:49             ` Jim Blandy
2006-01-31  3:12               ` Eirik Fuller
2006-01-31 21:48             ` Mark Kettenis
2006-02-01 17:52               ` Eirik Fuller
2006-02-01  6:04       ` Michael Snyder
2006-01-30 11:34 ` Andrew STUBBS
2006-01-30 11:42   ` Corinna Vinschen
2006-01-30 11:48     ` Andrew STUBBS
2006-01-31  2:23 ` Daniel Jacobowitz
2006-01-31  3:31   ` Eirik Fuller
2006-01-31  3:38     ` Daniel Jacobowitz
2006-02-07 22:05     ` Eirik Fuller
2006-02-20 15:52       ` Daniel Jacobowitz
2006-01-31  5:28   ` Jim Blandy
2006-01-31 13:59     ` Daniel Jacobowitz

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=8f2776cb0601302134w35cf9ae2v3cf03a4113fb3018@mail.gmail.com \
    --to=jimb@red-bean.com \
    --cc=davea@quasar.engr.sgi.com \
    --cc=eirik@hackrat.com \
    --cc=gdb-patches@sourceware.org \
    /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