From: James Dickens <jamesd.wi@gmail.com>
To: SystemTAP <systemtap@sources.redhat.com>
Subject: Fwd: R.F.C. Should we abandon User-land probes?
Date: Thu, 20 Oct 2005 20:06:00 -0000 [thread overview]
Message-ID: <cd09bdd10510201306q73329ba7oc127075c1662d62e@mail.gmail.com> (raw)
In-Reply-To: <cd09bdd10510201302i44a8a6fdy7f4cea33576bec0b@mail.gmail.com>
oops meant that to go to the mailing list as well
---------- Forwarded message ----------
From: James Dickens <jamesd.wi@gmail.com>
Date: Oct 20, 2005 3:02 PM
Subject: Re: R.F.C. Should we abandon User-land probes?
To: "Frank Ch. Eigler" <fche@redhat.com>
On 10/20/05, Frank Ch. Eigler <fche@redhat.com> wrote:
> Hi -
>
> > No I want to access components of complex structures that are pasted
> > to user land functions. [...]
>
> http://sources.redhat.com/bugzilla/show_bug.cgi?id=905
yes those work fine in kernel code, since variables to access
components of the structs/unions are allready availible for the
systemtap code and tapsets, but that is not the case of userland,
especially in the case of C++ classes/struct. So the user required to
enable guru-mode.
perhaps, you can enable guru-mode for including structs, but this of
course can polute the namespace.
James
> - FChE
>
>
>
next prev parent reply other threads:[~2005-10-20 20:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 18:16 James Dickens
2005-10-20 18:53 ` Frank Ch. Eigler
2005-10-20 19:08 ` James Dickens
[not found] ` <20051020192356.GD2761@redhat.com>
[not found] ` <cd09bdd10510201302i44a8a6fdy7f4cea33576bec0b@mail.gmail.com>
2005-10-20 20:06 ` James Dickens [this message]
2005-10-20 20:14 ` Fwd: " Martin Hunt
2005-10-20 20:18 ` James Dickens
2005-10-20 20:20 ` Fwd: " James Dickens
2005-10-20 20:45 ` Martin Hunt
2005-10-21 16:01 ` Frank Ch. Eigler
2005-10-20 22:31 ` Richard J Moore
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=cd09bdd10510201306q73329ba7oc127075c1662d62e@mail.gmail.com \
--to=jamesd.wi@gmail.com \
--cc=systemtap@sources.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).