Trapping an Access Violation

Thread View: borland.public.cppbuilder.nativeapi

5 messages

[T] Back to Threads [V] Tree View [G] Group Articles

5 total messages Started by Denville Longhurst Fri, 26 May 2006 15:44

#3537

Author: Denville Longhurst
Date: Fri, 26 May 2006 15:44

22 lines
1945 bytes

Hi

I have a slight problem with an application which throws an access violation 
very infrequently.  I have been unable to recreate it in the lab, and 
whenever it is reported to me, the reporter has no knowledge of the 
information contained in the access violation window - generally they just 
re-boot and walk away.

Can I trap an access violation in such a way that I can log the detail (eg 
violation at xxxx read of yyyy).  I can't think how to formulate the 
exxception handler, and where to put it so that it would be 
application-wide.  I note with interest that the try/catch block around 
Application->Initialize(); etc in the Project Source .cpp doesn't catch such 
an exception, since the application continues to run (albeit crippled) both 
during and following closure of the exception notification window.  Further, 
any timers continue to fire (as you would expect during the display of a 
form), in this case keeping a watch-dog alibe even though the program has 
effectively ceased functioning.

Many thanks,

Denville.

Re: Trapping an Access Violation

#3549

Author: Remy Lebeau (TeamB)
Date: Fri, 26 May 2006 17:52

18 lines
1386 bytes

"Denville Longhurst" <Denville@metco.co.uk> wrote in message
news:44772251$1@newsgroups.borland.com...

> Can I trap an access violation in such a way that I can log the detail

Have a look at third-party crash loggers, such as MadExcept
(http://www.madexcept.com).

> I note with interest that the try/catch block around
Application->Initialize();
> etc in the Project Source .cpp doesn't catch such an exception, since the
> application continues to run

Have you tried using the TApplication::OnException event yet?


Gambit

Re: Trapping an Access Violation

#3546

Author: Boba
Date: Fri, 26 May 2006 18:29

20 lines
1510 bytes

"Denville Longhurst" <Denville@metco.co.uk> wrote in message
news:44772251$1@newsgroups.borland.com...
> Hi
>
> I have a slight problem with an application which throws an access
violation
> very infrequently....
> ... the reporter has no knowledge of the  information contained in the
access
violation window

are you sure it is the TApplication causing that AV?
there are system tools allowing logging allmost all types of events like
that.
ask the user to e-mail you Dr.Watson's report. many times I've been
through
this type of situations when eventualy another yet bug in the OS itself
was
discovered.

Re: Trapping an Access Violation

#3551

Author: Denville Longhurst
Date: Fri, 26 May 2006 21:32

28 lines
1757 bytes

Thank you

"Boba" <Boba@somewhere.world> wrote in message 
news:44772b41$1@newsgroups.borland.com...
>
> "Denville Longhurst" <Denville@metco.co.uk> wrote in message
> news:44772251$1@newsgroups.borland.com...
>> Hi
>>
>> I have a slight problem with an application which throws an access
> violation
>> very infrequently....
>> ... the reporter has no knowledge of the  information contained in the
> access
> violation window
>
> are you sure it is the TApplication causing that AV?
> there are system tools allowing logging allmost all types of events like
> that.
> ask the user to e-mail you Dr.Watson's report. many times I've been
> through
> this type of situations when eventualy another yet bug in the OS itself
> was
> discovered.
>
>
>
>

Re: Trapping an Access Violation

#3552

Author: Denville Longhurst
Date: Fri, 26 May 2006 21:33

24 lines
1676 bytes

Thank you

"Remy Lebeau (TeamB)" <no.spam@no.spam.com> wrote in message 
news:4477423f$1@newsgroups.borland.com...
>
> "Denville Longhurst" <Denville@metco.co.uk> wrote in message
> news:44772251$1@newsgroups.borland.com...
>
>> Can I trap an access violation in such a way that I can log the detail
>
> Have a look at third-party crash loggers, such as MadExcept
> (http://www.madexcept.com).
>
>> I note with interest that the try/catch block around
> Application->Initialize();
>> etc in the Project Source .cpp doesn't catch such an exception, since the
>> application continues to run
>
> Have you tried using the TApplication::OnException event yet?
>
>
> Gambit
>
>

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads