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=13610>. 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=13610 Multiple Threads using XalanTransformer::transform() cause coredump ------- Additional Comments From [EMAIL PROTECTED] 2002-10-28 16:03 ------- It seems to work! Performed 20 times: 4 threads making 200 transformations, no core-dump. I assume that memory stream transformation is solved by this as well. I just recompiled the Xalan library, not Xerces. Is it enough? They talk about consistency of using this definition. --------------------------------------- from: /opt/aCC/html/C/guide/threads.htm Using -D__HPACC_THREAD_SAFE_RB_TREE ... Since changing the rb_tree implementation to make it thread safe would break binary compatibility, the preprocessing macro, __HPACC_THREAD_SAFE_RB_TREE, must be defined. Whether or not this macro is defined when compiling a file that includes the tree header, its use must be consistent. For example, a new object file compiled with the macro defined should not be linked with older ones that were compiled without the macro defined. Library providers whose library is built with the the macro defined may need to notify their users to also compile their source with the macro defined when the tree header is included.
