FreeTDS Development Group

[Vince ODea <vinceodea AT yahoo.com>]

Thanks Edmundo,

Here's what this gives:

Core was generated by `tsql'.
Program terminated with signal 11, Segmentation fault.
warning: The shared libraries were not privately mapped; setting a
breakpoint in a shared library will not work until you rerun the program.
#0  0xc02f72f8 in __errno () from /usr/lib/nls/iconv/methods.2/lsbucs2.sl
(gdb) where
#0  0xc02f72f8 in __errno () from /usr/lib/nls/iconv/methods.2/lsbucs2..sl
#1  0xc02236f0 in iconv () from /usr/lib/libc.2
#2  0x2ced0 in tds_iconv ()
#3  0x7b04a798 in ?? ()
#4  0x785f7074 in ?? ()
Cannot access memory at address 0xffffffee.
(gdb)





________________________________
From: Edmundo Robles L. <erobles AT sensacd.com.mx>
To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
Sent: Wednesday, November 26, 2008 7:26:08 PM
Subject: Re: [freetds] Need some help connectiing to MSSQL with tsql

in the prompt shell
first do:

gdb tsql core

after that, input the word 'where' in the gdb prompt '(gdb)'



Ing. Edmundo Robles Lopez.
Analista Programador.

--




-----Original Message-----
From: freetds-bounces AT lists.ibiblio.org on behalf of Vince ODea
Sent: Wed 11/26/2008 1:02 PM
To: FreeTDS Development Group
Subject: Re: [freetds] Need some help connectiing to MSSQL with tsql

Hi James,

None of the other tools work either. They all core dump.
How do I get a "Backtrace" or run tsql under gdb?

Cheers
Vince




________________________________
From: James K.. Lowden <jklowden AT freetds.org>
To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
Sent: Tuesday, November 25, 2008 3:02:39 PM
Subject: Re: [freetds] Need some help connectiing to MSSQL with tsql

Vince ODea wrote:
>  
> # TDSVER=7.0 /usr/local/freetds/bin/tsql -H X.X.X.X  -p 20482  -U User
> # -P Pass
> locale is "C C C C C C"
> locale charset is "roman8"
> Memory fault(coredump)

Please try to get a backtrace either from the .core file or by running
tsql under gdb, to discover the function that failed.  It shouldn't be
possible to engender a memory fault under any circumstances.  

The problem might lie in tsql itself.  Not all libtds functions check
their inputs, because that's considered the responsibility of the API
layer.  You might want to try one of the other tools: bsqldb, fisql,
freebcp, and see how they behave.  

--jkl
_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds



      
_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds