FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> From: Emile Heitor [mailto:imil AT isdnet.net]
> Sent: September 5, 2002 12:13 PM
> 
> > Now wait just a cotton pickin' minute.  tsql crashes 
> logging in?  That was
> > fixed on or about 6 August.  What's the date on your snapshot?
> 
> just cvs'ed this morning: $ head -1 ChangeLog
> Thu Sep  5  14:04:09 CEST 2002  Frediano Ziglio 
> <freddy77 AT angelfire.com>

Unable to reproduce, Emile:

$head -1 ChangeLog
Thu Sep  5  07:21:44 CEST 2002  Frediano Ziglio <freddy77 AT angelfire.com>
$tsql -S spquant -U LowdenJK -P $P
Msg 5703, Level 0, State 1, Server NTS0214, Line 0
Changed language setting to us_english.
1> select convert( varchar(50), @@version)
2> go

Microsoft SQL Server  7.00 - 7.00.859 (Intel X86)
1>

Are you using a big endian client?  (Mine is i386.)

Also note well the default --prefix changed the other day.  No chance you're
picking up an old tsql, is there?   

If you're sure about your setup, I guess we'd better have a look at your
backtrace....

Regards, 

--jkl

> > tsql shouldn't crash logging in.  That would be tembarrassing.
> 
> but it does :/
> after a little debugging, I saw the crash occurs in src/tds/token.c :
> 
>         tdsdump_log(TDS_DBG_FUNC, "%L inside 
> tds_process_login_tokens()\n");
>         /* get_incoming(tds->s); */
>         do {
>                 marker=tds_get_byte(tds); <---- Here
>                 switch(marker) {
>                         case TDS_AUTH_TOKEN:


The information contained in this transmission may contain privileged and
confidential information and is intended only for the use of the person(s)
named above.  If you are not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, any
review, dissemination, distribution or duplication of this communication is
strictly prohibited. If you are not the intended recipient, please contact
the sender immediately by reply e-mail and destroy all copies of the
original message. Please note that for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not be
responsible for carrying out such orders and/or instructions. Kindly refrain
from sending orders or instructions by e-mail unless you have confirmed that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming e-mail
correspondence of staff members serving certain functions.