public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jan.smets at nokia dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/103730] New: ubsan: store with insufficient space for an object of type Date: Wed, 15 Dec 2021 09:47:19 +0000 [thread overview] Message-ID: <bug-103730-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103730 Bug ID: 103730 Summary: ubsan: store with insufficient space for an object of type Product: gcc Version: 12.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: jan.smets at nokia dot com CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org, jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org Target Milestone: --- Following testcase produces an ubsan runtime error in GCC 10.2/11.3/trunk gcc test.c -o /tmp/test -O2 -Wall -Wextra -fsanitize=undefined && /tmp/test typedef int (logger_args_to_string)(void *event, void *pEntry); typedef struct logger_msginfo { #if 1 // OK when excluded void *test; #endif logger_args_to_string *Fn; } logger_msginfo; logger_msginfo x; logger_msginfo *logger = &x; void call( void ) { logger->Fn = (logger_args_to_string*) 0x1234; // Happy ((logger_msginfo *) & logger[0])->Fn = (logger_args_to_string*) 0x1234; // Happy ((logger_msginfo *) & logger)->Fn = (logger_args_to_string*) 0x1234; // store with insufficient space... , trunk gives array-bounds warning here too - but not on the line above. } int main(void) { call(); return 0; }
next reply other threads:[~2021-12-15 9:47 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-15 9:47 jan.smets at nokia dot com [this message] 2021-12-15 9:56 ` [Bug sanitizer/103730] " jakub at gcc dot gnu.org 2021-12-15 10:06 ` jan.smets at nokia dot com 2021-12-15 10:07 ` jakub at gcc dot gnu.org
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-103730-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).