From: Daniel Jacobowitz <drow@false.org>
To: Mark Kettenis <mark.kettenis@xs4all.nl>
Cc: dits365@gmail.com, gdb@sources.redhat.com
Subject: Re: What exactly does "info sharedlibrary" command show?
Date: Tue, 29 Aug 2006 21:24:00 -0000 [thread overview]
Message-ID: <20060829212354.GA31606@nevyn.them.org> (raw)
In-Reply-To: <200608292107.k7TL7tab029171@elgar.sibelius.xs4all.nl>
On Tue, Aug 29, 2006 at 11:07:55PM +0200, Mark Kettenis wrote:
> Yup, if you can guarantee that the first segment indeed includes all
> the .text code, the latter is much better.
How would you feel about "the segment containing .text", then?
Actually, I'd probably try first to pick out "the segment with exec
permission", and only if there was none or more than one look for a
section named .text; I see that this would work for OpenBSD too. I'm
trying as a general background task to decrease reliance on section
names; for instance, the ARM compilers only call this ER_RO.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-08-29 21:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-29 12:03 chen free
2006-08-29 12:40 ` Daniel Jacobowitz
2006-08-29 19:15 ` Mark Kettenis
2006-08-29 19:28 ` Daniel Jacobowitz
2006-08-29 20:06 ` Mark Kettenis
2006-08-29 20:12 ` Daniel Jacobowitz
2006-08-29 21:05 ` Steve Eaton
2006-08-29 21:17 ` Daniel Jacobowitz
2006-08-29 21:08 ` Mark Kettenis
2006-08-29 21:24 ` Daniel Jacobowitz [this message]
2006-08-30 5:22 ` chen free
2006-08-30 12:39 ` Daniel Jacobowitz
2006-08-30 13:24 ` chen free
2006-08-29 12:47 ` Frederic RISS
2006-08-29 13:00 ` chen free
2006-08-29 13:20 ` Frederic RISS
2006-08-29 13:36 ` chen free
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=20060829212354.GA31606@nevyn.them.org \
--to=drow@false.org \
--cc=dits365@gmail.com \
--cc=gdb@sources.redhat.com \
--cc=mark.kettenis@xs4all.nl \
/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