public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "mhiramat at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/3672] Support formatted dump of kernel structures
Date: Fri, 15 Aug 2008 23:40:00 -0000	[thread overview]
Message-ID: <20080815233525.14538.qmail@sourceware.org> (raw)
In-Reply-To: <20061207014705.3672.mmlnx@us.ibm.com>


------- Additional Comments From mhiramat at redhat dot com  2008-08-15 23:35 -------
(In reply to comment #2)
> Another possible syntax for this is inspired by the $$vars introduced
> recently.  Expanding struct contents could be represented like so:
> 

How about $$$var syntax?
It also could compose $$vars as $$$vars, or $$$parms.
and depth also be increased by adding $. ($$$$var)

>     $var$  =>  a string representation of $var's fields: like
>                0xfoo
>           or   {.foo=0xbeef, .zoo=0xp00}

I like latter format :-)

Thanks,

-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=3672

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

  parent reply	other threads:[~2008-08-15 23:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07  3:56 [Bug translator/3672] New: " mmlnx at us dot ibm dot com
2008-03-18  1:40 ` [Bug translator/3672] " fche at redhat dot com
2008-08-15 23:30 ` fche at redhat dot com
2008-08-15 23:40 ` mhiramat at redhat dot com [this message]
2009-06-17 18:58 ` [Bug translator/3672] Support formatted dump of struct $pointers fche at redhat dot com
2009-11-05 18:29 ` fche at redhat dot com
2009-11-10 19:00 ` jistone at redhat dot com

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=20080815233525.14538.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --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).