From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/2307] binary tracing
Date: Mon, 20 Feb 2006 03:00:00 -0000 [thread overview]
Message-ID: <20060220030004.3474.qmail@sourceware.org> (raw)
In-Reply-To: <20060209035522.2307.fche@redhat.com>
------- Additional Comments From fche at redhat dot com 2006-02-20 03:00 -------
It seems to me that an approach along these lines will not satisfy optimized
tracing along IBM's original request (re. struct support in the language), nor
permit much or any translator assistance to provide metadata to a binary
decoder. I consider it a technically weak solution.
On the other hand, just extending printf with binary formatting directives
should be easy, and not cause adverse interference with other future designs.
So, if people want to experiment with this part, go ahead.
--
What |Removed |Added
----------------------------------------------------------------------------
Status|WAITING |NEW
Last reconfirmed|0000-00-00 00:00:00 |2006-02-20 03:00:04
date| |
http://sourceware.org/bugzilla/show_bug.cgi?id=2307
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2006-02-20 3:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-09 3:55 [Bug translator/2307] New: " fche at redhat dot com
2006-02-17 6:53 ` [Bug translator/2307] " guanglei at cn dot ibm dot com
2006-02-17 10:55 ` hiramatu at sdl dot hitachi dot co dot jp
2006-02-17 15:32 ` guanglei at cn dot ibm dot com
2006-02-19 5:01 ` jrs at us dot ibm dot com
2006-02-20 3:00 ` fche at redhat dot com [this message]
2006-02-21 8:43 ` hunt at redhat dot com
2006-02-21 8:43 ` hunt 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=20060220030004.3474.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).