From: Mark Geisert <mark@maxrnd.com>
To: cygwin-patches@cygwin.com
Subject: [PATCH] Cygwin: Fix gmondump formatting goofs
Date: Mon, 14 Mar 2022 17:47:30 -0700 [thread overview]
Message-ID: <20220315004730.15783-1-mark@maxrnd.com> (raw)
The rewrite of %X to %p was malhandled. Fix that/them.
---
winsup/utils/gmondump.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/winsup/utils/gmondump.c b/winsup/utils/gmondump.c
index ec9db0598..2d29e826d 100644
--- a/winsup/utils/gmondump.c
+++ b/winsup/utils/gmondump.c
@@ -162,7 +162,7 @@ gmondump1 (char *filename)
note ("file %s, gmon version 0x%x, sample rate %d\n",
filename, hdr.version, hdr.profrate);
- note (" address range 0x%p..0x%p\n", hdr.lpc, hdr.hpc);
+ note (" address range %p..%p\n", hdr.lpc, hdr.hpc);
note (" numbuckets %d, hitbuckets %d, hitcount %d, numrawarcs %d\n",
numbuckets, hitbuckets, hitcount, numrawarcs);
@@ -175,7 +175,7 @@ gmondump1 (char *filename)
int incr = (hdr.hpc - hdr.lpc) / numbuckets;
for (res = 0; res < numbuckets; ++bucket, ++res, addr += incr)
if (*bucket)
- note (" address 0x%p, hitcount %d\n", addr, *bucket);
+ note (" address %p, hitcount %d\n", addr, *bucket);
bucket -= numbuckets;
if (numrawarcs)
@@ -186,7 +186,7 @@ gmondump1 (char *filename)
error (0, "unable to read rawarc data");
note (" rawarc data follows...\n");
for (res = 0; res < numrawarcs; ++rawarc, ++res)
- note (" from 0x%p, self 0x%p, count %d\n",
+ note (" from %p, self %p, count %d\n",
rawarc->raw_frompc, rawarc->raw_selfpc, rawarc->raw_count);
}
}
--
2.35.1
next reply other threads:[~2022-03-15 0:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 0:47 Mark Geisert [this message]
2022-03-16 7:43 ` Corinna Vinschen
2022-03-17 3:06 ` Mark Geisert
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=20220315004730.15783-1-mark@maxrnd.com \
--to=mark@maxrnd.com \
--cc=cygwin-patches@cygwin.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).