public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "shaohua.li at inf dot ethz.ch" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/109313] New: Incorrect line number in Use-After-Scope report Date: Tue, 28 Mar 2023 07:43:11 +0000 [thread overview] Message-ID: <bug-109313-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109313 Bug ID: 109313 Summary: Incorrect line number in Use-After-Scope report Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: shaohua.li at inf dot ethz.ch 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: --- For the following code, Asan reports an incorrect line number at -O1 and above. Compiler explorer: https://godbolt.org/z/KsroWf9M6 % cat -n a.c 1 int a, b; 2 int main() { 3 int *c=&a; 4 b = 0; 5 for (; b < 1; b++) { 6 int d=1; 7 c = &d; 8 if (a) 9 break; 10 } 11 if (*c) { 12 int e[1]={2}; 13 return e[0]; 14 } 15 } % % gcc-tk -O0 -fsanitize=address a.c && ./a.out ================================================================= ==1==ERROR: AddressSanitizer: stack-use-after-scope on address 0x7f2293700030 at pc 0x0000004012de bp 0x7ffca6ef0690 sp 0x7ffca6ef0688 READ of size 4 at 0x7f2293700030 thread T0 #0 0x4012dd in main /a.c:11 ... % % gcc-tk -O1 -fsanitize=address a.c && ./a.out ================================================================= ==1==ERROR: AddressSanitizer: stack-use-after-scope on address 0x7f7c4d200020 at pc 0x0000004011ee bp 0x7fff0179f250 sp 0x7fff0179f248 READ of size 4 at 0x7f7c4d200020 thread T0 #0 0x4011ed in main /a.c:5 ... %
next reply other threads:[~2023-03-28 7:43 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-03-28 7:43 shaohua.li at inf dot ethz.ch [this message] 2023-03-28 17:57 ` [Bug sanitizer/109313] " pinskia 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-109313-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).