From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 20223 invoked by alias); 31 Mar 2003 15:41:59 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 20198 invoked by uid 48); 31 Mar 2003 15:41:58 -0000 Date: Mon, 31 Mar 2003 15:52:00 -0000 Message-ID: <20030331154158.20197.qmail@sources.redhat.com> To: fr33z3@sources.redhat.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gmx.net@sources.redhat.com, nobody@gcc.gnu.org From: bangerth@dealii.org Reply-To: bangerth@dealii.org, fr33z3@sources.redhat.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, gmx.net@sources.redhat.com, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: c++/10269: ncurses function in class causes malloc() syscall to loop infinitly X-SW-Source: 2003-03/txt/msg02116.txt.bz2 List-Id: Synopsis: ncurses function in class causes malloc() syscall to loop infinitly State-Changed-From-To: open->feedback State-Changed-By: bangerth State-Changed-When: Mon Mar 31 15:41:58 2003 State-Changed-Why: I don't have the necessary libraries and header files installed on my system, so can't test. However, I think it's a bug in your code: in this part of your code if (1) { mask omask; omask.~mask(); } The destructor of omask is called twice. Since you do some memory deallocation there, I would not be entirely surprised if that would lead to strange effects later on. Can you say what happens if you fix this? W. http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10269