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/95693] [8/9/10/11 Regression] Incorrect error from undefined behavior sanitizer
Date: Tue, 16 Jun 2020 06:57:43 +0000	[thread overview]
Message-ID: <bug-95693-4-Ev249SckVn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-95693-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95693

Martin Liška <marxin at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
                 CC|                            |jason at gcc dot gnu.org,
                   |                            |mpolacek at gcc dot gnu.org,
                   |                            |nathan at gcc dot gnu.org
     Ever confirmed|0                           |1
   Last reconfirmed|                            |2020-06-16

--- Comment #1 from Martin Liška <marxin at gcc dot gnu.org> ---
Thank you for the report!
The error is newly printed with r8-7149-g2e1a7ecb2d8f1ee3.

Backtrace is here:
g++ pr95693.C -fsanitize=undefined -g && ./a.out 
pr95693.C:17:22: runtime error: reference binding to null pointer of type 'int'
    #0 0x4011fb in Derived::Derived()
/home/marxin/Programming/testcases/pr95693.C:17
    #1 0x401135 in main /home/marxin/Programming/testcases/pr95693.C:24
    #2 0x7ffff7147cc9 in __libc_start_main ../csu/libc-start.c:308
    #3 0x401079 in _start (/home/marxin/Programming/testcases/a.out+0x401079)

I'm not a C++ expert, but it seems to me an invalid code.

  parent reply	other threads:[~2020-06-16  6:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16  5:12 [Bug c++/95693] New: " gcc-90 at tbilles dot hu
2020-06-16  6:43 ` [Bug sanitizer/95693] [8/9/10/11 Regression] " rguenth at gcc dot gnu.org
2020-06-16  6:57 ` marxin at gcc dot gnu.org [this message]
2020-06-16  7:24 ` jakub at gcc dot gnu.org
2020-06-16  8:41 ` redi at gcc dot gnu.org
2021-01-14  9:02 ` rguenth at gcc dot gnu.org
2021-01-14 12:58 ` nathan at gcc dot gnu.org
2021-01-21 13:50 ` jakub at gcc dot gnu.org
2021-01-22 18:05 ` cvs-commit at gcc dot gnu.org
2021-01-22 18:06 ` [Bug sanitizer/95693] [8/9/10 " jakub at gcc dot gnu.org
2021-01-29 19:19 ` cvs-commit at gcc dot gnu.org
2021-01-29 19:24 ` [Bug sanitizer/95693] [8/9 " jakub at gcc dot gnu.org
2021-04-20 23:31 ` cvs-commit at gcc dot gnu.org
2021-04-22 16:49 ` cvs-commit at gcc dot gnu.org
2021-04-22 17:06 ` jakub at gcc dot gnu.org
2021-04-23 14:14 ` gcc-90 at tbilles dot hu

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-95693-4-Ev249SckVn@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: 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).