On Feb 22, 2005, at 7:05 AM, David Cargill wrote:
My initial ideas to resolve this are:
1) If we fail on creating a mutex (or locking a mutex or unlocking a mutex:
I mention these as well since they could also lead to an infinite loop in
XMLException) panic instead of throwing an exception.
I don't suspect this problem will occur very often (it was discovered with
a misaligned pointer that has since been corrected). I am currently
leaning towards (1) but thought I should get feedback from other people
before making this change. Anyone?
I agree with (1). Since we can't recover from having no mutex, failure to create one should be a fatal error. This shouldn't be a big issue, since we don't expect, on any architecture that I know of, to not be able to get one. As you indicate, the error occurred in your case only because of what was indeed a fatal logic error in the program.
-jdb
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
