Skip to Content.
Sympa Menu

freetds - Re: Crash in tsql

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: Crash in tsql
  • Date: Tue, 13 Aug 2002 09:46:18 -0400


> From: Brian Bruns [mailto:camber AT ais.org]
> Sent: August 12, 2002 10:37 AM
>
> > sizeof(*tds) differed between the two, I
> > just didn't have time to finish it off. config.h should be
> > included from tds.h (tds.h.in) otherwise we'll have this
> > problem again in the future.
>
> Actually, this fix is bad, since we don't distribute config.h
> (nor should we) things won't build.

Brian,

I don't understand that sentence. Could you unpack it for me, please?

> We simply can't be checking HAVE_ICONV in tds.h (or any distributable
> header). We could substitute from configure but that strikes me as
> sloppy. Any other options?

It's not obvious to me what's a "distributable" header and what's not, or
how HAVE_ICONV is any different from, say, the tests for gethostbyname_r().


Pretty clearly, we want the HAVE_ICONV test to be done in the configure
script, and the code to react accordingly. I gather that the way we were
doing that was causing a problem, but I don't understand what's defeating
your attempts to fix it.

Regards,

--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