Skip to Content.
Sympa Menu

freetds - Re: dberrhandler() and dbmsghandler()

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: "'TDS Development Group'" <freetds AT franklin.metalab.unc.edu>
  • Subject: Re: dberrhandler() and dbmsghandler()
  • Date: Fri, 6 Sep 2002 13:25:35 -0400


> From: Steven J. Backus [mailto:backus AT math.utah.edu]
> Sent: September 6, 2002 1:00 PM
>
> This reminds me of another problem I have with freetds. Here's the
> msg_handler I use:
>
...
> This puppy crashes under freetds, but not with sybase's tds. It
> happens like this:
>
> dbmsghandle(msg_handler); /* install msg_handler */
>
> dbuse(dbproc, "db"); /* Crash occurs at this line */
>
> I've bt'd in gdb and the line that's blowing up is:
>
> if (strlen(srvname) > 0)
> fprintf (ERR_CH, "Server '%s', ", srvname);
>
> The strlen is core dumping because srvname isn't initialized. Any
> chance of getting this fixed? I forget to comment out this line
> until a user calls me complaining.

Steve,

If you will post a simple test program evincing the problem when linked with
the most recent snapshot, I will look at it. The current code in
src/tds/token.c::tds_process_msg() looks clean, but maybe under some
circumstances it fetches a corrupted servername?

--jkl


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.






Archive powered by MHonArc 2.6.24.

Top of Page