From: fche@redhat.com (Frank Ch. Eigler)
To: Stan Cox <scox@redhat.com>
Cc: systemtap@sourceware.org
Subject: Re: PATCH add more syntax for shared library probing
Date: Thu, 24 Mar 2011 16:50:00 -0000 [thread overview]
Message-ID: <y0md3lgqx8e.fsf@fche.csb> (raw)
In-Reply-To: <4D8A0D75.9080600@redhat.com> (Stan Cox's message of "Wed, 23 Mar 2011 11:10:45 -0400")
scox wrote:
> [...]
Looks good!
> 2. Similar for -L. Perhaps filling in the wildcard with the matched
> library would be useful.
Yup. pp() etc. should get the fully resolved name.
> [...]
> +/* For each entry in the .dynamic section in the current module call 'callback', use
> + * 'data' for the dynamic entry buffer return the entry type and 'object' in case
> + * 'callback' is a method */
> [...]
This ld.so-emulation code looks promising, but the risk of giving
results inconsistent with actual ld.so would have to be guarded
against. Have you considered PR12560's alternate approach?
- FChE
prev parent reply other threads:[~2011-03-24 16:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-23 15:12 Stan Cox
2011-03-24 16:50 ` Frank Ch. Eigler [this message]
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=y0md3lgqx8e.fsf@fche.csb \
--to=fche@redhat.com \
--cc=scox@redhat.com \
--cc=systemtap@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).