Oops, I guess I did send this in about a month ago. At least I now know the duration of my long term "memory". :)
What do you mean by "static construction"? I am building Xerces as a statically linked library, but I've used it that way for months before I introduced this bug. Adam Heinz Senior Software Developer Exstream Software -----Original Message----- From: James Berry [mailto:[EMAIL PROTECTED] Sent: Friday, April 09, 2004 10:45 AM To: [EMAIL PROTECTED] Subject: Re: transcoding crash on mac On Apr 9, 2004, at 8:10 AM, Adam Heinz wrote: > [ Xerces 2.3.0 and 2.4.0, Mac 9.2 (via 10.2), Codewarrior 8.3 ] > > I'm getting a crash "unmapped memory exception" on my first call to > transcode. Hi Adam, Is this the same as your bug report #27669: http://issues.apache.org/bugzilla/show_bug.cgi?id=27669. The situation looks similar, but in that bug report you state you're not able to reproduce the issue with a simple test case. Can you review? Also, in that bug report I asked you about the state of the memory manager being passed into the call--I'm still suspicious of that. One thing that would cause the memory manager to be bad at that point would be if static construction was turned off in your CodeWarrior environment. Is that the case? James. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
