[freetds] Server dumps core while reading login packet
brian at bruns.com
brian at bruns.com
Wed Apr 14 20:01:19 EDT 2004
Steve: my webmail is showing your messages as empty, so I know you
sent a follow up to this but I can't read it.
The server accepts TDS 4.2/5.0 and 7.0 logins, however beyond that
some of the 7.0 stuff is missing. TDS 5.0 does work however.
As part of my super-secret mystery project, I'm about to pick up some
of the TDS 7.0 stuff again, but probably not in a time frame conducive
to what you are doing.
On Tue, 13 Apr 2004 21:41:11 -0400, "James K. Lowden" wrote:
> On Tue, 13 Apr 2004, Steve Kirkendall <skirkendall at dsl-only.net>
> > I'm trying to write a simple SQL server so Windows users can run
> > Reports on data in my company's Linux application.
> Welcome, Steve.
> > Last week I wrote the SQL interpreter,
> You may appreciate that's not a sentence I read every day....
> > and now I'm trying to use -ltdssrv to make it a server.
> I wonder if SQLite would be any use?
> I would be fun to see our server implementation bolted in front of
> something moderately useful.
> > They crash while trying to read strings for the login packet. My
> > SQL server dies while reading the client's host_name (the very
> > string), while the unittest program fails while reading the
> > after successfully reading the host_name and user_name. In one
> > I think unittest.c failed while reading user_name, but I'm not 100%
> > about that. Both programs die while trying to free the old value
> > that string, when the old value is bogus.
> > Is this a known problem? Or is it just me?
> It's almost just you. The reason you're having trouble searching the
> archives, and why there's no documentation, is that our server
> implementation has seen very little use. As you surmise, all the
> been on the client side.
> Of course, this leaves the field wide open for any contribution you'd
> to make.
> Brian wrote what's there, afaik. I probably runs only TDS 4.2. If
> trying something else, that could result in a segfault. Still, the
> test should oughta work.
> > Oh, one other little problem: The tsql program seems to ignore the
> > -pportnumber flag. I tried using -p1433 to make it use the same
> > as MS SQL Server, but it insists on using port 4000.
> Look again at the man page. The port option is paired with the -H
> option. It doesn't affect the -S servername option. It could reject
> -S, I suppose, but instead it just doesn't listen.
> FreeTDS mailing list
> FreeTDS at lists.ibiblio.org
More information about the FreeTDS