> Hi Keith, > Thanks for the reply. The function in question calls the > XalanDOMString.transcode() function to get a CharVectorType back. Then > the function allocates a char[] of appropraite length, and then it > copies characters from the vector into the array one by one. When the > function tries to return, I get an Access Violation. Looking at the > stack trace, it appears that the violation occurs in the vector's > deconstructor method. >
This is a pretty clear indication that you are not building with the correct run-time library options. For the release configuration, you need to use /MD and link with the release version of the Xalan-C and Xerces-C libraries. For the debug configuration, you need to use /MDd, and link with the debug version of the Xalan-C and Xerces-C libraries. The debug versions of the libraries have a "D" appended to the prefix. For example, Xalan-C_1D.lib, instead of Xalan-C_1.lib. Dave
