FreeTDS Development Group

[Brian Bruns <camber AT ais.org>]

Steve,

James Cameron fixed it on Jan 12 according to the ChangeLog, I followed up 
last night with a quick hack to return a error message to the client app 
(using the tds_client_msg() function).  So now if the client apps sets the 
callbacks before login (which SQSH does nicely) we'll get:

Server 'foo' not found!

which means that FreeTDS could resolve the servername to a useful IP 
address the by normal means.  In no cirumstance should we now be 
segfaulting.  So grabbing the nightly snapshot or CVS may provide some 
enlightenment on the subject.

Additionally, I merged some patches (openlink sent in their changes), 
added TDSPool to the autoconf stuff and added a configuration file to 
control it.  So, once I work out a few more nuances with tdspool, I'll put 
out a 0.54pre1

Brian

On Tue, 22 Jan 2002, Steve Langasek wrote:

> Hi Richard,
> 
> On Tue, Jan 22, 2002 at 01:55:07PM -0600, Richard Rowell wrote:
> > > ./sqsh -S servername -U username
> > > it asks for my password and after I enter it, it immediately segfaults.
> 
> > I get segfaults when I specify an incorrect server name.  I have also 
> > seen 
> > similar things happen with the stock libraries shipped with my distro 
> > (debian).  You may want to make sure you don't have any old libraries 
> > sitting 
> > around.  
> 
> I had been under the impression that these segfaults have been cleared 
> up for a while.  Are you still seeing segfaults under Debian when using 
> a current version of the FreeTDS package (freetds0 0.52+0.53pre2-2 or 
> 0.53-2) and the sqsh package (2.1-2)?  If so, please file a bug against
> the package (or provide me with the necessary info on-list), as I would
> like to get this fixed before I accidentally run into it. :)
> 
> Steve Langasek
> postmodern programmer
>