Sahan Gamage wrote:
If I am writing to incorrect mailing list then thousand apologies.
probably ;-) but...
I am writing a module to host Apache Axis2C inside Apache2 server.
Axis2C heavily uses dynamic loaded libraries. I have compiled the
module and ran successfully on Linux platform. But in Win32 platform
the module crashes. It seems that the crash occurs when the process
tries to load libxml2.dll (which is the xml parser used in Axis2C).
Well then it looks like you will have to take this up with the Axis2C
devs, but...
Here's the stack trace for the crash
NTDLL! 77f51baa()
NTDLL! 77f7561d()
axis2_http_transport_utils_process_http_post_request(axis2_environment
* * 0x1001a514 _axis2_env, axis2_msg_ctx * 0x00dc6d00, axis2_stream *
0x00dc65b0, axis2_stream * 0x00dc5350, char * 0x0097c246, int 595,
char * 0x0097c1a4, char * 0x00dc53a0) line 201 + 24 bytes
This is a classic flaw of enabling /Oy (implied by /O2) - and you probably
want to change add the /Oy- compile flag so you can see the -entire- traceback
on the libs that are hiding this information.
As for critical sections, that looks like a flaw in libxml2, or in the
manner that it is initialized by axis2c, and either way I'd suggest getting
better traceback info and then moving your discussion there.
Bill
