dblib assertion crash on connection timeouts
Daniel Fazekas <[email protected]>
| Newsgroups | gmane.comp.db.tds.freetds |
|---|---|
| Message-ID | <[email protected]> |
I think it would be preferable if dblib in the current development version wouldn't just crash the host process with an assertion if a connection attempt times out. dbutil.c:193: _dblib_check_and_handle_interrupt: Assertion `dbproc != ((void *)0) && !dbdead((dbproc))' failed. For example, doing a bsqldb -S microsoft.com or trying any other firewalled or non-responsive address. Returning INT_CANCEL on DBDEAD in _dblib_check_and_handle_interrupt seems to be nicer.