Re: [reSIProcate] catch(...) in Encryption manager
Agreed. We should not do catch (...) anywhere in the library. I think
Daniel is looking into this.
Jason
On 10/20/05, Justin Matthews <justin.matthews@xxxxxxx> wrote:
> 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
>
> _______________________________________________
> resiprocate-devel mailing list
> resiprocate-devel@xxxxxxxxxxxxxxxxxxx
> https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel
>