Hi,
I see that STLport 4.5.3 does not define this __node_alloc class
as anything other than most 'static' functions either. I suspect that
possibly I am getting a protection exception with a larger number of
clients objects being serviced a bunch of different threads because my
application is trying to access a the libxalan DLL and in this DLL is a
bunch of static node allocations and on zOS each thread is not a whole
separate process ( like on Linux). So, to the DLL, if he gets a whole bunch
of MutableNodeRefList vectors to allocate , he doesn't know who is who
unless they are all totallyseparate in time. Does this sound remotely
reasonable as to why I might get a protection exception in __node_alloc?
Could this be changed in the future so that multi-threaded applications
don't just die on this? Even though I have my own separate copy in each
thread of the document, this is still happening. Any suggestions?
Thanks,
Suzanne
