From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug runtime/7051] New: printf %n directive broken
Date: Tue, 25 Nov 2008 16:50:00 -0000 [thread overview]
Message-ID: <20081125164829.7051.fche@redhat.com> (raw)
ksebasti found several issues with this widget:
printf ("%n%4d", 0) prints 0x04 0x00 0x00 0x00 0x00
printf ("%n%n%n") prints junk
printf ("%n") prints junk
If we keep %n around at all, it needs to compose sensibly.
We could make it mean "total record length", so that the
previous three cases would print
printf ("%n%4d", 0) would print 0x05 0x00 0x00 0x00 0x00
printf ("%n%n%n") would print 0x03 0x03 0x03
printf ("%n") would print 0x01
--
Summary: printf %n directive broken
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: runtime
AssignedTo: systemtap at sources dot redhat dot com
ReportedBy: fche at redhat dot com
http://sourceware.org/bugzilla/show_bug.cgi?id=7051
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2008-11-25 16:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 16:50 fche at redhat dot com [this message]
2008-12-02 9:47 ` [Bug runtime/7051] " prerna at linux dot vnet dot ibm dot com
2008-12-02 9:49 ` prerna at linux dot vnet dot ibm dot com
2008-12-02 18:06 ` [Bug runtime/7051] remove broken printf %n directive support fche at redhat dot com
2008-12-05 19:12 ` ksebasti at redhat dot com
2008-12-29 19:23 ` prasad at linux dot vnet dot ibm dot com
2008-12-29 19:24 ` prasad at linux dot vnet dot ibm 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=20081125164829.7051.fche@redhat.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).