It seems to me that Allocate() may think you're out of memory. How
you managed to run out of memory in a 64-bit application is quite
unclear to me. It seems more likely that the heap has been corrupted.
It's possible to override logog's memory allocation routines with a
custom allocator. This would allow you to trap out of memory
conditions without using exception handlers, if you're allergic to
them.
> --
> You received this message because you are subscribed to the Google Groups
> "Logog" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to
logog+un...@googlegroups.com.
> To post to this group, send email to
lo...@googlegroups.com.
> Visit this group at
http://groups.google.com/group/logog.
> For more options, visit
https://groups.google.com/d/optout.
--
---
John Byrd
Gigantic Software
2102 Business Center Drive
Suite 210-D
Irvine, CA 92612-1001
http://www.giganticsoftware.com
T:
(949) 892-3526 F:
(206) 309-0850