From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug runtime/31074] On aarch64 the systemtap.base/set_kernel.stp triggers "Unable to handle kernel paging request"
Date: Fri, 01 Dec 2023 17:19:19 +0000 [thread overview]
Message-ID: <bug-31074-6586-eCL7Cp459M@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-31074-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=31074
Mark Wielaard <mark at klomp dot org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mark at klomp dot org
--- Comment #7 from Mark Wielaard <mark at klomp dot org> ---
(In reply to William Cohen from comment #6)
> On aarch64 sizeof('\0') is returning 4 rather than 1 as expected for a
> character.
That is actually so on all arches. The confusing thing is that a character
constant has type int. Which explains why sizeof ('a') is really sizeof (int)
== 4. While char c = 'a'; sizeof (c) == 1 (sizeof (char)).
Note that C and C++ differ here. In C++ character constants are type char and
so this program:
#include <stdio.h>
int
main ()
{
printf ("sizeof literal char: %d\n", sizeof ('a'));
}
$ gcc -g -o c c.c
$ ./c
sizeof literal char: 4
$ g++ -g -o c c.c
$ ./c
sizeof literal char: 1
Aren't C and C++ fun? :)
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-12-01 17:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-17 17:13 [Bug runtime/31074] New: " wcohen at redhat dot com
2023-11-22 0:19 ` [Bug runtime/31074] " fche at redhat dot com
2023-11-22 15:02 ` wcohen at redhat dot com
2023-11-22 15:36 ` fche at redhat dot com
2023-11-27 16:07 ` wcohen at redhat dot com
2023-12-01 14:51 ` wcohen at redhat dot com
2023-12-01 16:45 ` wcohen at redhat dot com
2023-12-01 17:19 ` mark at klomp dot org [this message]
2023-12-04 16:38 ` wcohen 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-31074-6586-eCL7Cp459M@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).