From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Received: (qmail 5603 invoked by uid 71); 11 Jan 2003 08:56:01 -0000 Date: Sat, 11 Jan 2003 08:56:00 -0000 Message-ID: <20030111085601.5602.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: John Ahlgren Subject: Re: ada/9273: g++ 3.2 generates segmentation fault for correct code Reply-To: John Ahlgren X-SW-Source: 2003-01/txt/msg00708.txt.bz2 List-Id: The following reply was made to PR ada/9273; it has been noted by GNATS. >>From john.ahlgren@home.se Mon Jan 13 00:57:20 2003 From: John Ahlgren To: gcc-gnats@gcc.gnu.org Cc: Subject: Re: ada/9273: g++ 3.2 generates segmentation fault for correct code Date: 11 Jan 2003 09:50:32 +0100 Hi, I'm sorry about my bug report; it is invalid. I made the assumption that no object of A was copied, but that was the case. So, may I now bother you asking why it is copied: class A { ... }; A a; vector avec; // avec.reserve(2) (*) avec.push_back(a); avec.push_back(a); With (*) of course nothing is copied, but even so, can't realloc() be used instead? Cheers, John On Sat, 2003-01-11 at 09:06, gcc-gnats@gcc.gnu.org wrote: > Thank you very much for your problem report. > It has the internal identification `ada/9273'. > The individual assigned to look at your > report is: unassigned. > > >Category: ada > >Responsible: unassigned > >Synopsis: g++ 3.2 generates segmentation fault for correct code > >Arrival-Date: Sat Jan 11 00:06:00 PST 2003 >