Alex wrote: >>
Hi,
I recommend you to enable "Use Debug DCUs" option as outlined here:
http://blog.eurekalog.com/?p=122 Right now it looks like your code has called invalid routine. That's because exception was raised at $01339A31 which do not belong to any module. And CPU code and dump looks gibberish.
This can be due to many reasons: - DLL was unloaded and you've called routine in this DLL.
- Your stack was corrupted and ret command redirect your execution path to some random location. This can be due to: a). You use static local arrays and out of bounds (be sure to use "Range check errors").
b). You use routine with wrong prototype (for example, stdcall instead of cdecl or similar).
Those are just examples. This may be something else as well. It's hard to tell, not seeing any code and not knowing about your application.
I also recommend you to use some memory debugger tool (like FastMM or SafeMM) to be sure that you do not have any memory corruption bug in your application.
-- Alex Best regards...
Alexander - *EurekaLog Support Team* ---------------------------------------------------------------------- -- Alex's Profile:
http://news.eurekalog.com/member.php?userid=24316 View this thread:
http://news.eurekalog.com/showthread.php?t=2526 << Alex, thanks for the info. I downloaded & included the latest fastMM and built my app with debug dcus. By just starting and closing my app I get a large number of small leaks, all of which come from Borland units, and some of which involve unknown functions. This doesn't sound hopeful.
Any ideas where I go from here? I understand that fastMM is supported
on one of the embarcadero forums, so I'll take a look there now.
Jeremy
--