What type of exception is it? Is it a bona-fide C++ exception, where a C++ module actually throws an exception, or is it a Windows SE exception (Access violation, or some OS exception)?
If it's the latter, then you could try the catch-all:
But you should really fix the problem with your app if it's an OS exception.Code:try
{
}
catch(...)
{
}
I know that no socket functions throws exceptions explicitly, since they are all 'C' functions. The only exceptions possible are the ones generated by the OS (called Structured Exceptions). There is no guarantee, unless you set the proper compile switches, that these are caught (don't remember what these settings are). But at some point, you have to address these exceptions, and they are an indication that your program is faulty.
Regards,
Paul McKenzie

