From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <ecos-devel-return-1587-listarch-ecos-devel=sources.redhat.com@ecos.sourceware.org>
Received: (qmail 29759 invoked by alias); 12 Aug 2009 19:07:28 -0000
Received: (qmail 29676 invoked by uid 22791); 12 Aug 2009 19:07:27 -0000
X-SWARE-Spam-Status: No, hits=-2.1 required=5.0 	tests=AWL,BAYES_00,SPF_PASS
X-Spam-Check-By: sourceware.org
Received: from hagrid.ecoscentric.com (HELO mail.ecoscentric.com) (212.13.207.197)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 12 Aug 2009 19:07:21 +0000
Received: from localhost (hagrid.ecoscentric.com [127.0.0.1]) 	by mail.ecoscentric.com (Postfix) with ESMTP id 5E6B82F7802C; 	Wed, 12 Aug 2009 20:07:18 +0100 (BST)
Received: from mail.ecoscentric.com ([127.0.0.1]) 	by localhost (hagrid.ecoscentric.com [127.0.0.1]) (amavisd-new, port 10024) 	with ESMTP id 8hsXJPn+SvmH; Wed, 12 Aug 2009 20:07:17 +0100 (BST)
Date: Wed, 12 Aug 2009 19:07:00 -0000
Message-Id: <pn4osc6ecb.fsf@delenn.bartv.net>
From: Bart Veer <bartv@ecoscentric.com>
To: Uwe Kindler <uwe_kindler@web.de>
CC: ecos-devel@sourceware.org, jifl@jifvik.org
In-reply-to: <4A830092.7050206@web.de> (message from Uwe Kindler on Wed, 12 	Aug 2009 19:49:06 +0200)
Subject: Re: Strange __cxa_pure_virtual problem
References:  <4A830092.7050206@web.de>
Mailing-List: contact ecos-devel-help@ecos.sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <ecos-devel.ecos.sourceware.org>
List-Subscribe: <mailto:ecos-devel-subscribe@ecos.sourceware.org>
List-Post: <mailto:ecos-devel@ecos.sourceware.org>
List-Help: <mailto:ecos-devel-help@ecos.sourceware.org>, <http://ecos.sourceware.org/lists.html#faqs>
Sender: ecos-devel-owner@ecos.sourceware.org
X-SW-Source: 2009-08/txt/msg00017.txt.bz2

>>>>> "Uwe" == Uwe Kindler <uwe_kindler@web.de> writes:

    Uwe> Hello Jonathan,
    Uwe> thank you for your detailed description - it helped me to find the 
    Uwe> cause. In ustlecos.cpp there is a function:

    Uwe> void diag_print_exception(const exception& ex)
    Uwe> {
    Uwe>          static string exstr(64);
    Uwe> ...

    Uwe> if I remove the static from the string declaration the 
    Uwe> __cxa_pure_virtual problem is gone.

What happens if you then try to link a trivial eCos application which
declares a static string object? I suspect that is going to pull in
__cxa_guard_release() again, which will take its __cxa_pure_virtual()
from libsup++.a instead of libtarget.a. So deleting the static from
the declaration is only moving the problem, not solving it.

Bart

-- 
Bart Veer                                   eCos Configuration Architect
eCosCentric Limited    The eCos experts      http://www.ecoscentric.com/
Barnwell House, Barnwell Drive, Cambridge, UK.      Tel: +44 1223 245571
Registered in England and Wales: Reg No 4422071.