From: "mmlnx at us dot ibm dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/3672] New: Support formatted dump of kernel structures
Date: Thu, 07 Dec 2006 03:56:00 -0000 [thread overview]
Message-ID: <20061207014705.3672.mmlnx@us.ibm.com> (raw)
Add a function or extend printf to dump a kernel structure in a human readable
format, similar to what gdb can do. Does dwarf give us enough info to do this
without requiring the script to specify the structure type?
For example, something like this:
print_struct($sock)
where $sock is a pointer to a struct socket could output this:
{
state = 1,
flags = 6,
ops = 0x83337444,
fasync_list = 0x84435355,
file = 0x54338234,
sk = 0x73322556,
wait = {
lock = 1,
task_list = {
next = 0x822334455,
prev = 0x855443322
},
},
type = 0
}
--
Summary: Support formatted dump of kernel structures
Product: systemtap
Version: unspecified
Status: NEW
Severity: enhancement
Priority: P2
Component: translator
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: mmlnx at us dot ibm dot com
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.
next reply other threads:[~2006-12-07 1:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-07 3:56 mmlnx at us dot ibm dot com [this message]
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
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=20061207014705.3672.mmlnx@us.ibm.com \
--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).