From: Robb Romans <robb@linux.vnet.ibm.com>
To: Martin Hunt <hunt@redhat.com>
Cc: SystemTap <systemtap@sources.redhat.com>
Subject: Re: Language Reference, updated
Date: Wed, 06 Dec 2006 17:14:00 -0000 [thread overview]
Message-ID: <87bqminj5s.fsf@skyhawk.austin.ibm.com> (raw)
In-Reply-To: <1164736330.3660.31.camel@dragon> (Martin Hunt's message of "Tue, 28 Nov 2006 12:52:10 -0500")
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
>>>>> "MH" == Martin Hunt <hunt@redhat.com> writes:
MH> 9.1.4 SHould mention that normal printf field formatting is
MH> available (%-20, %o, %x, etc). Also mention %p and binary
MH> formats here.
Martin,
I've incorporated your feedback into the Language Reference, but I'd
like clarification on one section. What do you mean by "Also mention %p
and binary formats here" ?
Here is a description of %p for standard C:
"Pointer to a pointer. Inputs a memory address in the same fashion of the
%p type produced by the printf function."
Is there a difference in SystemTap's handling of %p that you want me to
call out, or is there a special usage case that you have in mind?
Is there a difference in SystemTap's handling of printing binary streams
versus C standard syntax? Thanks.
Regards,
Robb
- --
Robb Romans (512) 838-0419
Linux Commando T/L 678-0419
robb@linux.vnet.ibm.com ARS NA5TT
.-- - ..-. ..--..
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>
iD8DBQFFdeA/ZyOifwSFgjQRAmCYAJ0a185d7j7jaZt93Ts7cYiZTrPeSwCgtzis
igXOlANUokjF8PxHV59JSPE=
=67Bh
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-12-05 21:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-24 21:52 Robb Romans
2006-11-29 1:07 ` Martin Hunt
2006-11-29 7:44 ` Robb Romans
2006-12-06 17:14 ` Robb Romans [this message]
2006-12-06 18:41 ` Martin Hunt
2006-12-06 19:51 ` Robb Romans
2006-12-12 20:45 ` Mike Mason
2007-01-31 0:02 ` Robb Romans
2007-02-12 19:22 ` Robb Romans
2007-02-13 19:54 ` Frank Ch. Eigler
2007-02-16 23:59 ` Mike Mason
2007-02-17 0:39 ` Stone, Joshua I
2007-02-22 20:59 ` Robb Romans
2007-02-27 17:58 ` Mike Mason
2007-02-27 18:08 ` Robb Romans
2007-02-27 19:03 ` Robb Romans
2006-12-12 21:24 Stone, Joshua I
2006-12-12 22:19 ` Frank Ch. Eigler
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=87bqminj5s.fsf@skyhawk.austin.ibm.com \
--to=robb@linux.vnet.ibm.com \
--cc=hunt@redhat.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).