From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id ECA27383C7F4; Tue, 13 Dec 2022 14:17:29 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org ECA27383C7F4 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1670941049; bh=FMZczJ6oXSmIeXzhwUaY9Y7E8muJPLTOVrdvtm0JyCw=; h=From:To:Subject:Date:In-Reply-To:References:From; b=SjgA7M/RmRFgGxpN+exxdMw/1LllBYrxvf1t8zQ4kGuySwilfva8xPdK7cYdsOxWC rzuk+732CYgQljTXHVo1gOBJhOhuNWCIYNbb9B7KZfR45tQ8w/NHk2zhSkbJm8YbXT STyIp4hfMjQLWNqKdCZX2gOwUlqe6zuouJ2QGS4I= From: "ssofroni at cytanet dot com.cy" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/108083] Code with memory leak does not get triggered when I run the executable Date: Tue, 13 Dec 2022 14:17:29 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 12.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ssofroni at cytanet dot com.cy X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D108083 --- Comment #1 from stefanos --- I forgot to mention that if I try *directly* the following command g++ -Wall -Wextra -Werror -Wpedantic -std=3Dc++20 -g -g0 -fsanitize=3Daddress,undefined -D_GLIBCXX_DEBUG -fno-strict-aliasing -fwrap= v -lm -o tmp src/tmp.cpp in place of Makefile, it triggers the memory leak.=