Google Search:

< Previous by Date	Date Index	Next by Date >
	Thread Index	Next in Thread >

[reSIProcate] catch(...) in Encryption manager

From: "Justin Matthews" <justin.matthews@xxxxxxx>
Date: Thu, 20 Oct 2005 11:02:26 -0400

Hi,

In encryptionmanager.cxx:288, catch(...) can cause serious debugging
headaches if a fatal exception occurs (at least on windows).  Can this
catchall be removed?

Thanks,

-Justin

Follow-Ups:
- Re: [reSIProcate] catch(...) in Encryption manager
  - From: Jason Fischl

Prev by Date: Re: [reSIProcate] u_int32_t
Next by Date: [reSIProcate] rmtrasport() ?
Previous by thread: [reSIProcate] Could use some more advice on how to use resip Stack....
Next by thread: Re: [reSIProcate] catch(...) in Encryption manager
Index(es):
- Date
- Thread