DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18542>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=18542

Deleting something returned by XMLString::transcode crashes when application is using 
the release build of Xerces-C++





------- Additional Comments From [EMAIL PROTECTED]  2003-04-01 19:10 -------
Hi.  As I promised, here is my update.

But before anything else, I have a question.  Is there any reason why the 
XercesLib project in 2.1.0 (and 2.2.0 for that matter) have to be linked with 
the DLL version of the runtime?  That is the reason why the debug build is 
dependent on msvcrtd.dll and msvcirtd.dll.  I tried building it with the static 
runtime and it still works.  Plus, it's not dependent on those two dlls 
anymore, of course.  And that means, we can now ship our product without 
worrying about that dependency.  Are we allowed to change the project 
settings?  I hope so as it is the only solution I've found so far.

(Below is optional reading as I don't think I want to pursue the idea of using 
2.2.0 anymore.  But if you'd like to, I'm fine with that too)

And now for the update, XMLString::release() worked with my code snippet.  When 
I linked 2.2.0 into my real project that also links the third-party library 
that I mentioned before, I was able to build it.  So that's cool.  However, one 
line in the code causes a crash:

hdrNode->setPrefix( bdyNode->getPrefix() );

It seems to have started another problem.  Don't know what it is yet.  Like I 
said, I don't think I want to pursue this anymore as I'm more interested now in 
my question above regarding changing the projects settings of XercesLib to link 
with the static runtime.

Thanks.  I really appreciate all your help.
Ever

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to