From: Daniel Jacobowitz <drow@false.org>
To: Jim Blandy <jimb@codesourcery.com>
Cc: gdb-patches@sourceware.org, Ulrich Weigand <uweigand@de.ibm.com>,
Pedro Alves <pedro_alves@portugalmail.pt>
Subject: Re: [rfc] Shared libraries over the remote protocol, take two
Date: Mon, 18 Jun 2007 19:38:00 -0000 [thread overview]
Message-ID: <20070618193854.GA29250@caradoc.them.org> (raw)
In-Reply-To: <m3lkehqcsx.fsf@codesourcery.com>
On Mon, Jun 18, 2007 at 12:31:58PM -0700, Jim Blandy wrote:
> With the following DTD:
>
> <!-- library-list: Root element with versioning -->
> <!ELEMENT library-list (library)*>
> <!ATTLIST library-list version CDATA #FIXED "1.0">
> <!ELEMENT library (segment)*>
> <!ATTLIST library name CDATA #REQUIRED>
> <!ELEMENT segment EMPTY>
> <!ATTLIST segment address CDATA #REQUIRED>
>
> there's no way to have several segments at different offsets, because
> segments aren't allowed to have names. Shouldn't segments have a name
> attribute?
I don't think we need to name them to do that. If we did, we'd have
to define meanings for the names, and so forth...
<library-list>
<library name="libc.so.1">
<segment address="0x4000"/>
<segment address="0x10000"/>
</library>
</library-list>
The first one will be the first PT_LOAD from the ELF file, et cetera.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-06-18 19:38 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 15:02 Daniel Jacobowitz
2007-06-18 19:32 ` Jim Blandy
2007-06-18 19:38 ` Daniel Jacobowitz [this message]
2007-06-18 22:04 ` Jim Blandy
2007-06-18 22:20 ` Daniel Jacobowitz
2007-06-18 20:05 ` Eli Zaretskii
2007-07-02 19:03 ` Daniel Jacobowitz
2007-06-18 20:10 ` Jim Blandy
2007-06-18 20:13 ` Jim Blandy
2007-06-18 20:33 ` Daniel Jacobowitz
2007-06-18 22:06 ` Jim Blandy
2007-06-18 21:13 ` Pedro Alves
2007-07-02 22:01 ` 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=20070618193854.GA29250@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=jimb@codesourcery.com \
--cc=pedro_alves@portugalmail.pt \
--cc=uweigand@de.ibm.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