Re: dblib assertion crash on connection timeouts

Frediano Ziglio <[email protected]> Fri, 20 Mar 2015 10:21:37 +0000

Newsgroups	gmane.comp.db.tds.freetds
Message-ID	<CAHt6W4eYkXLzgC9wrMjk2+Z7BXPmDfj0ANemHuL0R_nxWqAf+w@mail.gmail.com>

2015-03-07 18:03 GMT+00:00 Daniel Fazekas <[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.


Removed the DBDEAD part and checked, not returns correctly timeout error

Frediano