From: David Smith <dsmith@redhat.com>
To: William Cohen <wcohen@redhat.com>
Cc: systemtap@sourceware.org
Subject: Re: Improve build-id checking when the task we're interested in isn't 'current'. git commit causing problems on ARM and IA64
Date: Tue, 03 Apr 2012 14:35:00 -0000 [thread overview]
Message-ID: <4F7B0A70.6030704@redhat.com> (raw)
In-Reply-To: <4F7A23DB.5000800@redhat.com>
On 04/02/2012 05:10 PM, David Smith wrote:
> It looks like on current kernels access_process_vm() is exported...
Which isn't true. On 3.4.0-0.rc0.git1.2.tip0.uprobes.fc18.x86_64, 'stap
-L' gets confused about which symbols are exported. I keep getting
excited about the new exports, then my hopes get cruelly dashed.
I'm still not sure how to solve this problem.
--
David Smith
dsmith@redhat.com
Red Hat
http://www.redhat.com
256.217.0141 (direct)
256.837.0057 (fax)
next prev parent reply other threads:[~2012-04-03 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-30 21:15 William Cohen
2012-04-02 19:30 ` David Smith
2012-04-02 20:17 ` William Cohen
2012-04-02 22:10 ` David Smith
2012-04-03 14:18 ` William Cohen
2012-04-03 14:35 ` David Smith [this message]
2012-04-04 20:57 ` Improve build-id checking when the task we're interested in isn't 'current'. git commit causing problems on ARM and IA64) David Smith
2012-04-05 15:29 ` David Smith
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=4F7B0A70.6030704@redhat.com \
--to=dsmith@redhat.com \
--cc=systemtap@sourceware.org \
--cc=wcohen@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).