Received: from localhost (postgresql.org [64.49.215.8]) by postgresql.org (Postfix) with ESMTP id D58D6475C3D for ; Tue, 15 Oct 2002 22:28:04 -0400 (EDT) Received: from news.hub.org (news.hub.org [64.49.215.80]) by postgresql.org (Postfix) with ESMTP id 783AE475AE5 for ; Tue, 15 Oct 2002 22:28:04 -0400 (EDT) Received: by news.hub.org (Postfix, from userid 8) id 41180381813; Tue, 15 Oct 2002 22:28:03 -0400 (EDT) From: JSavage@data-mate.com (Savage) X-Newsgroups: comp.databases.postgresql.interfaces Subject: PgDatabase, on heap construction results in SIGSEGV. Date: 15 Oct 2002 19:26:25 -0700 Organization: http://groups.google.com/ Lines: 12 Message-ID: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: groups-abuse@google.com To: pgsql-interfaces@postgresql.org X-Virus-Scanned: by AMaViS new-20020517 X-Archive-Number: 200210/58 X-Sequence-Number: 3220 I am having a problem constructing a PgDatabase object. If I create the object on the stack (as a var local to a function) then it constructs and connects to the DB ok. But, if I create and construct the object on the heap, a SIGSEGV occurs within libpq++.so.4. Has anyone got any ideas what could be causing this? I have only been programming under linux for a month or so at this stage, but I've a lot of Win32 experience. Any pointers to things that a Win32 to Linux newbie would not be aware of would be much appreciated. Thanks, John