public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "craig.ringer at 2ndquadrant dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/27187] Introduce user_buffer_hex and kernel_buffer_hex helpers in conversions tapsets
Date: Mon, 18 Jan 2021 03:59:22 +0000	[thread overview]
Message-ID: <bug-27187-6586-4lHbzF03G1@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27187-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27187

--- Comment #2 from Craig Ringer <craig.ringer at 2ndquadrant dot com> ---
Created attachment 13131
  --> https://sourceware.org/bugzilla/attachment.cgi?id=13131&action=edit
Docs x-ref for %.*M etc

Well, now I feel really, really dumb. Oh well, I learned some useful things.

Replacement patch attached that points this out in the docs for
user_buffer_quoted() and user_string().

I took a quick look to see if I could work out how to create a function::printf
and function::sprintf manpage to x-ref the stap(1) content, but didn't work out
a way to do so without injecting a tapset function for printf and sprintf.

I guess I could put them in a dummy tapset with no actual definitions or wedge
them into uconversions.stp, but neither seems very pretty.

Anyway, docs patch attached. I'll confirm whether it can fully replace my use
of user_buffer_hex.

-- 
You are receiving this mail because:
You are the assignee for the bug.

      parent reply	other threads:[~2021-01-18  3:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-15  1:59 [Bug tapsets/27187] New: " craig.ringer at 2ndquadrant dot com
2021-01-15  1:59 ` [Bug tapsets/27187] " craig.ringer at 2ndquadrant dot com
2021-01-15 21:46 ` fche at redhat dot com
2021-01-18  3:59 ` craig.ringer at 2ndquadrant dot com [this message]

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=bug-27187-6586-4lHbzF03G1@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --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).