From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9300 invoked by alias); 22 May 2011 14:24:26 -0000 Received: (qmail 9291 invoked by uid 22791); 22 May 2011 14:24:25 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,RFC_ABUSE_POST X-Spam-Check-By: sourceware.org Received: from mail-pw0-f47.google.com (HELO mail-pw0-f47.google.com) (209.85.160.47) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sun, 22 May 2011 14:24:12 +0000 Received: by pwj9 with SMTP id 9so2493312pwj.20 for ; Sun, 22 May 2011 07:24:11 -0700 (PDT) MIME-Version: 1.0 Received: by 10.142.144.5 with SMTP id r5mr675223wfd.384.1306074251228; Sun, 22 May 2011 07:24:11 -0700 (PDT) Received: by 10.142.255.6 with HTTP; Sun, 22 May 2011 07:24:11 -0700 (PDT) In-Reply-To: <20110522141654.GA26862@www2.mrbrklyn.com> References: <20110522141654.GA26862@www2.mrbrklyn.com> Date: Sun, 22 May 2011 14:31:00 -0000 Message-ID: Subject: Re: C++ template bugs in gcc 4.6 From: Jonathan Wakely To: Ruben Safir Cc: gcc-bugs@gcc.gnu.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2011-05/txt/msg01925.txt.bz2 On 22 May 2011 15:16, Ruben Safir wrote: > On Sun, May 22, 2011 at 02:29:08PM +0100, Jonathan Wakely wrote: >> re http://gcc.gnu.org/ml/gcc-bugs/2011-05/msg01899.html >> >> The gcc-bugs mailing list is for mails automatically generated by >> bugzilla, if you want to report a bug please do so in bugzilla, not by >> email. See http://gcc.gnu.org/bugs/ for instructions. >> >> If you want to ask for help using g++ then use the gcc-help mailing >> list, see http://gcc.gnu.org/lists.html >> > > > Can't be done. =A0It's not working, aside from the fact that this is too > complex of an example to fit within the parameters. It's working fine for me. As for too complex: nonsense. Did you bother to read the link I provided? You can attach preprocessed source, though you should really try to reduce it to a minimal testcase - I don't believe mysql++ is really necessary to demonstrate the problem. None of that changes the fact gcc-bugs is the wrong list. > I spent nearly 45 minutes gathering all the information together. =A0If > the post is not adequate, that is fine. =A0That's why i don't report bugs. Run your code under valgrind, it shows you were the first memory corruption occurs. If you don't want to report bugs then dont' be surprised if they don't get fixed.