Re: Strange __cxa_pure_virtual problem

Bart Veer <[email protected]>
Newsgroups gmane.os.ecos.devel
Message-ID <[email protected]>
>>>>> "Uwe" == Uwe Kindler <[email protected]> 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.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.