Hi, That's what EurekaLog does, but the line that is causing the error never shows up. This normally works with other errors, but does not seem to work with this one AV.
Is there any other Debug info that I can turn on in Delphi to try and get more details into the call stack? Thanks --- In [email protected], "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Hi, > I wuld suggest to use the Jedi-Library. I've built successfully a 'Debug' module that saves the stack information to disk in case of an unexpected Error. > The stored information leads back to the line of code which rose the error. > > Have fun > Bob > > > Hi All, > > > > What can I do to get the maximum information out of the call stack? > > I am getting an inconsistent AV that I need to find and fix. I have > > EurekaLog. Is there anything that I can do to get the maximum amount > > of information out of the call stack so that I can find this AV? > > > > It is starting to become a huge problem for me. I have never gotten > > it, but others using the program get it inconsistently. > > > > Thanks > > ----------------------------------------------------- Home page: http://groups.yahoo.com/group/delphi-en/ To unsubscribe: [EMAIL PROTECTED] Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/delphi-en/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
