Skip to Content.
Sympa Menu

freetds - RE: [freetds] 0.61 tsql core dump, locale = "C C C C C C"

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: 'FreeTDS Development Group' <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] 0.61 tsql core dump, locale = "C C C C C C"
  • Date: Mon, 12 May 2003 11:09:41 -0400

> From: ZIGLIO Frediano [mailto:Frediano.Ziglio AT mail.vodafone.it]
> Sent: May 12, 2003 10:07 AM

> > In addition, I'm getting warning errors on config.c, which
> > James Lowden
> > thinks probably indicate a 64-bit corruption that needs to be
> > fixed, and may be causing all of my problems:
> > cc: "config.c", line 842: warning 724: Assignment converts
> default int
> > return type to pointer "field".
> > cc: "config.c", line 849: warning 725: Assignment converts 32
> > bit integer to pointer "field".
>
> No, probably are related to strtok_r headers not included.
> Try doing a "man strtok_r" and see what header reports...

Freddy, just to confirm: We expect no 64-bit warnings, right? It's my
understanding that FreeTDS should compile cleanly on any 64-bit platform.

I told Dan I suspect, as you do, that we're failing to detect one of his
header files, and that these warning are a consequence of trying to compile
against an invalid prototype.

My theory is that some misalignment causes a 0 or 1 to be deposited in the
dump filehandle, resulting in log output going to stdout/stderr.

Dan, it might help to post your config.log.

--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 we do not accept account orders and/or instructions
by e-mail, and therefore will not be responsible for carrying out such orders
and/or instructions.






Archive powered by MHonArc 2.6.24.

Top of Page