Try EurekaLog. It will show you the EXACT line of code in your program which generated the error AND the flow of the program before the crash.
Alan Colburn wrote: > Hi folks -- > > As someone who's still a relative newbie, I'm having a difficult time > understanding the bugs in an application I wrote. The part that seems so > strange to me is that they only happen on Windows XP. I get the same errors > on different XP machines, while getting no errors when I try the application > on either Vista or Windows 2000. I installed a copy of madExcept to try > learning more but some of the report info is a bit beyond my abilities to be > helpful. > > Happily, the problems do fall into repeatable patterns. In one case the > culprit seems to be the @LStrClr function in Delphi (2006's) System unit. > This produces the kind of access violation you get when a method is > referencing memory set to 00000000. In the other case, the > TCustomClientDataSet.RecNo method calls TCustomClientDataSet.Check and > creates a DBClient exception with the message "at end of table." > > Beside the fact that I don't know much about Delphi's source code, the other > thing that makes these problems hard for me is that they don't happen on my > development machine (which is running Vista)--I cannot recreate them. > > Although I would be thrilled to receive whatever specific advice you'd care > to give, I would also be curious about general advice re: how to handle > errors that you can't reproduce. They must be common for anyone who has a > fairly sizable user base. > > Thanks, as always -- Al C. > > _______________________________________________ > Delphi mailing list -> [email protected] > http://lists.elists.org/cgi-bin/mailman/listinfo/delphi > > _______________________________________________ Delphi mailing list -> [email protected] http://lists.elists.org/cgi-bin/mailman/listinfo/delphi
