From: Roland McGrath <roland@redhat.com>
To: Mike Mason <mmlnx@us.ibm.com>
Cc: "Stone, Joshua I" <joshua.i.stone@intel.com>,
systemtap@sources.redhat.com
Subject: Re: Pointer chain paranoia
Date: Wed, 15 Nov 2006 10:06:00 -0000 [thread overview]
Message-ID: <20061114212854.028E8180059@magilla.sf.frob.com> (raw)
In-Reply-To: Mike Mason's message of Tuesday, 14 November 2006 13:12:08 -0800 <455A3128.4050509@us.ibm.com>
> Are pointer chain references in the regular stap language (not embedded
> C) always safe? In other words, if I use something of the form
> $ptr1->ptr2->ptr3->var, does stap automatically convert that to the
> needed deref() macros?
Yes, all generated references use the macro (that's why it exists).
next prev parent reply other threads:[~2006-11-14 21:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-14 18:36 Stone, Joshua I
2006-11-14 19:23 ` Vara Prasad
2006-11-14 19:25 ` Roland McGrath
2006-11-14 21:21 ` Mike Mason
2006-11-15 10:06 ` Roland McGrath [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-14 21:29 Stone, Joshua I
2006-11-14 18:33 Mike Mason
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=20061114212854.028E8180059@magilla.sf.frob.com \
--to=roland@redhat.com \
--cc=joshua.i.stone@intel.com \
--cc=mmlnx@us.ibm.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).