On Apr 9, 2004, at 9:17 AM, Adam Heinz wrote:
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.
Static construction refers to the runtime-triggered construction of C++ objects that are of global scope. Generally this is invoked by the same startup code that later invokes main(). On CodeWarrior that would generally be the chunk of code called __start, which should be set in your PPC linker panel in the field labeled main:
Since the memory manager passed to transcode at your point of failure is one that is global, my thinking was that your crash could be triggered if this object was not properly constructed (or not yet constructed) at the time of your call, due perhaps to the fact that static construction hadn't occurred.
James.
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]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
