[DUG] app terminating abruptly
Nahum.Wild
Nahum.Wild at PayGlobal.Com
Wed Nov 30 11:12:53 NZDT 2005
Use madExcept [http://www.madexcept.com/madExceptDescription.htm] it'll give
you a call stack for each thread running when the crash occurs. Since using
it our tricky unexplained crashes have turned into 'it crashed there, now
why did it do that' type problems.
Nahum.
> -----Original Message-----
> From: delphi-bounces at ns3.123.co.nz
> [mailto:delphi-bounces at ns3.123.co.nz] On Behalf Of Conor Boyd
> Sent: Wednesday, 30 November 2005 11:03 a.m.
> To: 'NZ Borland Developers Group - Delphi List'
> Subject: RE: [DUG] app terminating abruptly
>
> In terms of logging, you could look at tracing using the
> OutputDebugString method in the Windows unit (D5 anyway).
>
> If you're outputting stuff via that method, you could pick it
> up in realtime and remotely using something like DebugView
> from Sysinternals
> (http://www.sysinternals.com/Utilities/DebugView.html)
>
> HTH,
>
> Conor
>
> -----Original Message-----
> From: delphi-bounces at ns3.123.co.nz
> [mailto:delphi-bounces at ns3.123.co.nz] On Behalf Of Robert martin
>
> You might also want to log where your code is running in a
> file log, this might give you a hint as to where the error is
> occurring.
>
> [snip]
>
> _______________________________________________
> Delphi mailing list
> Delphi at ns3.123.co.nz
> http://ns3.123.co.nz/mailman/listinfo/delphi
>
More information about the Delphi
mailing list