public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/98669] SIGSEGV on pc=0 in crypt() with -fsanitize=address Date: Thu, 14 Jan 2021 08:15:48 +0000 [thread overview] Message-ID: <bug-98669-4-vWnRWBIdaT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-98669-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98669 Martin Liška <marxin at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |WAITING Ever confirmed|0 |1 Last reconfirmed| |2021-01-14 CC| |doko at gcc dot gnu.org --- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> --- Thank you for the report. However, I can't reproduce that on openSUSE Tumbleweed with GCC 10 installed: $ g++-10 pr98669.C -lcrypt -fsanitize=address -g && ./a.out sasWQy9ecMDEs same for older compilers: $ g++-7 pr98669.C -lcrypt -fsanitize=address -g && ./a.out sasWQy9ecMDEs $ g++-9 pr98669.C -lcrypt -fsanitize=address -g && ./a.out sasWQy9ecMDEs @doko: Can you please try to reproduce that?
next prev parent reply other threads:[~2021-01-14 8:15 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-14 7:40 [Bug sanitizer/98669] New: " marko.makela at mariadb dot com 2021-01-14 8:15 ` marxin at gcc dot gnu.org [this message] 2021-01-14 9:32 ` [Bug sanitizer/98669] " marko.makela at mariadb dot com 2021-01-14 10:25 ` doko at debian dot org 2021-01-14 10:36 ` doko at debian dot org 2021-01-14 10:43 ` marxin at gcc dot gnu.org 2021-01-14 10:51 ` marxin at gcc dot gnu.org 2021-01-14 10:52 ` doko at debian dot org 2021-01-14 10:56 ` marxin at gcc dot gnu.org 2021-01-14 11:39 ` doko at debian dot org 2021-01-14 11:45 ` jakub at gcc dot gnu.org 2021-01-14 13:11 ` doko at debian dot org 2021-01-14 13:35 ` marxin at gcc dot gnu.org 2021-01-14 16:25 ` marko.makela at mariadb dot com 2022-09-06 7:05 ` asn at samba dot 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-98669-4-vWnRWBIdaT@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).