Dantzler, DeWayne C wrote:
I rebuilt Xerces and captured the build output in a log file. I searched the
log file and found the lines
========================================================================
Compiling xercesc/util/NetAccessors/Curl/CurlNetAccessor.cpp
Compiling xercesc/util/NetAccessors/Curl/CurlURLInputStream.cpp
========================================================================
So, it appears that the curl NetAccessor was built with Xerces. I'll include
the entire build log since maybe something else is missing. As to why Xerces is
not using the curl NetAccessor, I'm at a lost since the configure script and
build seems to have worked. I must be missing something. Is there a feature on
the parser to force it to use a specific NetAccessor? What other info can I
provide to help track down why Xerces issues the bus error on parse?
#1 0xc9e0fe74 in xercesc_3_0::SocketNetAccessor::makeNew (this=0x4001eb40,
urlsour...@0x400401f8, httpInfo=0x0) at ./xercesc/util/XMemory.hpp:107
So your xercesc library doesn't contain SocketNetAccessor after
compiling. But another library with SocketNetAccessor implementation
has been used by your program in runtime.
May be the problem is in this linker option (look at two different
xercesc folders):
-Wl,/net/sinai/home/d/dcd9420/labs/xercesLab/xerces-c-3.0.1/src/.libs:/site/sw/ots/curl/curl-7.19.6/lib:/site/ots/xerces/xerces-c-3.0.1/lib
Good luck!
Vitaly
