FreeTDS Development Group

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

From: Steve Dumbrell [mailto:steve.dumbrell AT cogent.bnpparibas.com.au]
Sent: February 19, 2003 10:19 PM

> I am getting a "Bus error(coredump)" unless I explicity specify the
location of the freetds.conf with the -I switch.
>  
> Eg If I type the command:
>  
>      tsql -SCAD2000 -Usa -Psecret
-I/var/cd/test/powermart/admin/freetds.conf it works.
>  
> If however I export FREETDSCONF=/var/cd/test/powermart/admin/freetds.conf 
and then run the command:
>  
>      tsql -SCAD_2000 -Usa -Psecret                  
>  
> I get the follow response:
> 
> locale is "C C C C C C"
> charset is "roman8"
> Bus error(coredump)
>  
> The operating system is HPUX 11.0

Steve, 

I would like to see this fixed.  Could you do two things for me?  

1.  Tell us the version you're using, or date of snapshot.  
2.  Run a backtrace of the error, thus:

$ gdb tsql
gdb> r -SCAD_2000 -Usa -Psecret
 [error message]
gdb> bt
 [interesting feedback]
gdb> quit

That will help us track down the offending pointer.  You might have to
recompile freetds with debugging symbols included, to get a useful
backtrace.  

By the way, the '"locale is "C C C C C C"' message is not a good sign.  It
means setlocale(3) is returning a bogus string.  Steve Langasek fixed how
setlocale(3) is initialized on 13 January 2003, in revision 1.48 of tsql.c.
If your version is older than that, you might want to upgrade and see if the
problem goes away.  But that's most likely a separate issue.  

Regards, 

--jkl

P.S.  Please post only plaintext messages to the list if you can.  


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.