From: Jim Keniston <jkenisto@us.ibm.com>
To: argetek senvx <argetek.senvx@gmail.com>
Cc: systemtap@sourceware.org
Subject: Re: Workarounds for very useful developer userspace tracing scripts
Date: Sat, 09 Jun 2007 21:16:00 -0000 [thread overview]
Message-ID: <1181420180.3781.29.camel@ibm-ni9dztukfq8.beaverton.ibm.com> (raw)
In-Reply-To: <7d5f758c0706091312h7cc76be4o78225c046cdb9df2@mail.gmail.com>
On Sat, 2007-06-09 at 21:12 +0100, argetek senvx wrote:
> Thanks, Jim!
>
> Although a bit painful for folks like me not needing to mess with the
> kernel (anymore :-}), yet gotta admit this seems very very cool (not
> minding the interface - any stap guys listening? :-}).
Thanks. I think the possibilities of kprobes + uprobes + utrace +
SystemTap are indeed cool. I can assure you that stap guys are
listening.
>
> I patched my Ubuntu Feisty kernel 2.6.20-16-386 with the utrace patch
> set. Can you please point me to a uprobes patch that would apply to
> this cleanly?
>
> I also checked a *dry-run* application of your patch on a Fedora7 box
> I have remote access to (kernel 2.6.21-1.3194.fc7 has utrace already):
>
> ------------------------------------------------------------------------
>
> 2.6.21-1.3194.fc7-x86_64$ patch -up1 --dry-run < ~/uprobes.patch
>
[Patch tribulations snipped]
>
> Also, as you can see some of the files (probably added by the patch)
> prompt for a 'file to patch'. Am I missing something?
I assume you're looking at the May 25/26 posting I mentioned,
http://sources.redhat.com/ml/systemtap/2007-q2/msg00399.html
I was lazy and attached all 3 patches to that one post. On some
mailers, they don't show up as separate attachments. So the patch you
have may be all 3 patches concatentated. Each patch ends with a line
containing a lone underscore (_), so they should be easy to separate.
Just apply them in order. Was that the problem?
These patches should apply cleanly to any utrace-enabled kernel, with
the possible exceptions of the patches to the Makefiles and Kconfig
file, which should be easy to hand-patch.
>
> Regards,
>
> ~ argetek
Thanks again.
Jim
next prev parent reply other threads:[~2007-06-09 21:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 17:07 argetek senvx
2007-06-08 20:15 ` Jim Keniston
2007-06-09 20:12 ` argetek senvx
2007-06-09 21:16 ` Jim Keniston [this message]
2007-06-09 22:35 ` argetek senvx
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=1181420180.3781.29.camel@ibm-ni9dztukfq8.beaverton.ibm.com \
--to=jkenisto@us.ibm.com \
--cc=argetek.senvx@gmail.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).