From: "craig.ringer at 2ndquadrant dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/26249] New: [PATCH] uconversions format error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 5 has type ‘void *’ [-Werror=format=]
Date: Thu, 16 Jul 2020 10:23:48 +0000 [thread overview]
Message-ID: <bug-26249-6586@http.sourceware.org/bugzilla/> (raw)
https://sourceware.org/bugzilla/show_bug.cgi?id=26249
Bug ID: 26249
Summary: [PATCH] uconversions format error: format ‘%lx’
expects argument of type ‘long unsigned int’, but
argument 5 has type ‘void *’ [-Werror=format=]
Product: systemtap
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: tapsets
Assignee: systemtap at sourceware dot org
Reporter: craig.ringer at 2ndquadrant dot com
Target Milestone: ---
Please apply the following fix:
sed -i 's/user string copy fault at 0x%lx/user string copy fault at 0x%p/g'
tapset/uconversions.stp
to prevent this error on gcc 10.1.1 (Fedora 32):
/tmp/stapZ1uHM9/stap_35d624015b7561890f7e266d60669c82_7434_src.c: In function
‘function___global_user_string_n_warn__overload_1’:
/tmp/stapZ1uHM9/stap_35d624015b7561890f7e266d60669c82_7434_src.c:1139:40:
error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument
5 has type ‘void *’ [-Werror=format=]
1139 | "user string copy fault 0x%ld at %lx [man error::fault]", rc,
| ~~^
| |
| long unsigned int
| %p
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-07-16 10:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 10:23 craig.ringer at 2ndquadrant dot com [this message]
2020-07-16 11:11 ` [Bug tapsets/26249] " craig.ringer at 2ndquadrant dot com
2020-07-16 18:26 ` fche at redhat dot com
2020-07-17 2:30 ` craig.ringer at 2ndquadrant dot com
2020-07-20 1:41 ` craig.ringer at 2ndquadrant dot com
2020-07-20 1:42 ` craig.ringer at 2ndquadrant dot com
2020-07-29 0:30 ` fche 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=bug-26249-6586@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sourceware.org \
/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).