Re: Combined usage of exception handling
- From: Severian <severian@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 30 Mar 2005 16:41:58 GMT
On Wed, 30 Mar 2005 11:18:20 -0500, "William DePalo [MVP VC++]"
<willd.no.spam@xxxxxxxx> wrote:
>"asid" <asid369@xxxxxxxxxxx> wrote in message
>news:eWdISNUNFHA.3668@xxxxxxxxxxxxxxxxxxxxxxx
>> Does it make sense to use two different exception
>> handling mechanisms in the same application like
>> following?
>
>If you must. Realize that structured exceptions (__try, __catch) are almost
>always indicative of programming errors. Even if you catch one, by the time
>that you do, your application's state may be mucked up tp the point that it
>would have been better to crash and burn.
I use SEH to catch crashes, present a more useful error message to the
user, log the error, along with registers, a stack trace, thread
information, open files, a memory map, handle information, a list of
running programs, etc. (Whichever are possible in the current state.)
Of course, some really bad bugs can make any or all of this
impossible, but most of those are found prior to release.
--
Sev
.
- Follow-Ups:
- Re: Combined usage of exception handling
- From: William DePalo [MVP VC++]
- Re: Combined usage of exception handling
- References:
- Re: Combined usage of exception handling
- From: William DePalo [MVP VC++]
- Re: Combined usage of exception handling
- Prev by Date: Re: Combined usage of exception handling
- Next by Date: Re: VC71 bug: static call through object
- Previous by thread: Re: Combined usage of exception handling
- Next by thread: Re: Combined usage of exception handling
- Index(es):
Relevant Pages
|