Hello.
Thanks Stefan for your answer, we did it but we've got the same result (core
dumped :-) and
I realiy don`t know why the problem persist. We have solve the problem
changing the std library
used to link, linking with the std library "libstdc++-2-libc6.1-1-2.9.0"
explicitly (-l option in g++).
The default version (libstdc++-3-libc6.2-2-2.10.0) seems to have a bug or an
incompatibility.
We have found (using "ldd" command) that the example programs (DOMCount,
etc.) uses
"libstdc++-2-libc6.1-1-2.9.0" library instead of the default
(libstdc++-3-libc6.2-2-2.10.0.so), so
we add the comented option to the Makefile and we solve the problem... (!).
Well, thanks all
Harald.
----- Mensaje original -----
De: "Stefan Brauneis" <[EMAIL PROTECTED]>
Para: <[EMAIL PROTECTED]>
Enviado: martes 8 de mayo de 2001 13:09
Asunto: Re: xerces 1.4, DOM Parser, segmentation fault, std c++ library
version???
> Harald Barrera Dubois wrote:
>
> > Hi all.
> >
> > My version of the std c++ library is "libstdc++-2.96-69" (in Redhat
linux: rpm
> > -qa | grep std). The examples distributed with the xerces library runs
without
> > problems, but when I compile the source code of any example (for example
> > DOMCount), I receive "segmentation fault" error.
> > I suspect about the std c++ library because is there where the
segmentation
> > fault occurs in createReader member of ReaderMgr class.
> > Which version are you using?
> > Is this the correct version?
> > Someone is using the same version of stdlib?
>
> Hi,
>
> I think we had the same problem. We use redhat 7.0 with libstdc++--2.96-69
and
> gcc-2.96-69, the solution to our
> seg. fault problems was to recompile the whole xerces-library. So, I would
> propose to download the xerces sources and
> compile them with your version of gcc. After that try to compile the
examples as
> well if you want to use them.
> The reason should be that if you try to compile the samples on your
maschine they
> will be linked to the new libstc++ but
> the xerces library itself is linked to the old version. This should cause
some
> version confilicts which you can only avoid if both, the library and the
> programm(e.g. the sample) uses the same libstdc++. The other possibility
could be
> to downgrade your gcc. But afaIk I think this is not the easiest way.
> A pretty good documentation on how to compile the libary comes with the
sources
> so this shouldn't be a real problem.
> cu
> stefan
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
