unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: guile-devel <guile-devel@gnu.org>
Subject: Re: thinking out loud: wip-rtl, ELF, pages, and mmap
Date: Sun, 28 Apr 2013 14:45:11 +0200	[thread overview]
Message-ID: <87y5c2ddt4.fsf@pobox.com> (raw)
In-Reply-To: <874nevhe4a.fsf@pobox.com> (Andy Wingo's message of "Wed, 24 Apr 2013 22:23:33 +0200")

Hi,

On Wed 24 Apr 2013 22:23, Andy Wingo <wingo@pobox.com> writes:

> I'll change the linker to always emit sections and segments that
> correspond exactly in their on-disk layout and in their in-memory
> layout.  (In ELF terms: segments are contiguous, with p_memsz ==
> p_filesz.)  I'll put commonly needed things at the beginning, and
> debugging info and the section table at the end.  Then I'll just map
> the whole thing with PROT_READ, and set PROT_WRITE on those
> page-aligned segments that need it.  (Obviously in the future,
> PROT_EXEC as well.)
>
> Then I'll just record a list of ELF objects that have been loaded.

I've done this now.  If you are on wip-rtl, you will need to recompile
all of your .go files, as the loader now checks for these constraints.

> Simple bisection will map IP -> ELF, and from there we have the section
> table in memory (lazily paged in by the virtual memory system) and can
> find the symtab and other debug info.

I haven't done this yet, but at this point we can do it in Scheme I
think.

Regards,

Andy
-- 
http://wingolog.org/



  parent reply	other threads:[~2013-04-28 12:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-24 20:23 thinking out loud: wip-rtl, ELF, pages, and mmap Andy Wingo
2013-04-24 22:20 ` dsmich
2013-04-28 12:45 ` Andy Wingo [this message]
2013-04-28 15:23 ` Ludovic Courtès
2013-04-29  5:47 ` Nala Ginrut

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

  List information: https://www.gnu.org/software/guile/

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

  git send-email \
    --in-reply-to=87y5c2ddt4.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).