Hello Jörg, Thank you very much for the explanations. Well, we use std::containers in interfaces quite often. So this explains perfectly your problems.
Best regards,
Dom
Am Montag, 9. November 2009 schrieb Richter, Jörg:
> Hi Dom,
>
> >Do you have an idea why -D_GLIBCXX_DEBUG caused this? Does
> >this define change
> >symbol sizes that could lead to such a crash?
>
> I have been bitten by this problem before. But most of the time this
> results in link errors, not runtime errors. It is possible to link .o
> files with different _GLIBCXX_DEBUG setting together, provided that they
> use std-containers only in the implementation.
> But as soon as you use std-containers in the interface they are not
> compatible anymore.
>
> The internal name and the size of the container and iterators changes.
> If you use containers as members in .h files or as result-types of
> functions (whos type isn't encoded in the mangled name) than everything can
> happen.
>
>
> Jörg
--
**********************************************************************
Dominik Seichter - [email protected]
KRename - http://www.krename.net - Powerful batch renamer for KDE
KBarcode - http://www.kbarcode.net - Barcode and label printing
PoDoFo - http://podofo.sf.net - PDF generation and parsing library
SchafKopf - http://schafkopf.berlios.de - Schafkopf, a card game, for KDE
Alan - http://alan.sf.net - A Turing Machine in Java
**********************************************************************
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________ Podofo-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/podofo-users
