Try to use Eureka Log. Maybe it will give you some hints there the AV appears.
Anyway if you don't want to use Eureka or other debugger, you can use the AV's address to find the location manually. Use the 'Find error' menu to insert error's address. Delphi will send you to the procedure that generated the error. You need to have 'Debug information' inserted in your project, else it won't work. Darren McBride wrote: > Folks, > > I have an application that utilises separate packages for different aspects > of my application. Sometimes I get random access violations when it appears > that the only logical possibility is that, when running two instances of the > application, the packages from the first application instance appear to > corrupt memory addresses in the second application instance. I am not using > FastMM or anything (maybe I should) and am still using Delphi 6. Am I right > in assuming that separate instances of the BPL's are loaded into separate > memory addresses for each application instance ? Is there anything else I > can use to trace the problem ? > > I am very careful is using Assigned() when clearing objects and doing > everything by the book in my constructors and destructors. > > Thanks in advance, > Darren > > > > _______________________________________________ > Delphi mailing list -> [email protected] > http://www.elists.org/mailman/listinfo/delphi > > _______________________________________________ Delphi mailing list -> [email protected] http://www.elists.org/mailman/listinfo/delphi
