FreeTDS Development Group

[mark <snowdog AT zserve.com>]

On Monday 09 September 2002 06:12 pm, James K. Lowden wrote:
> On Mon, 9 Sep 2002 12:36:56 -0700, "mark" <snowdog AT zserve.com> wrote:
> > I'm getting sigsegv's in tds_submit_query (CVS HEAD updated this
> > morning).
> >
> > Just wondering if its possible that the connection is getting ruined
> > somehow either by the database closing it or what. Is there any way I
> > can test a TDSSOCKET object to make sure that it won't cause tds_*
> > functions to sigsegv?
>
> Has anyone reproduced this?  tsql works for me.
>
> Mark, what's the client architecture, and can you provide a backtrace?
>
> --jkl


I'm using Kylix 3, so the backtrace is kinda weird.

libpthread.pthread_mutex_lock + 0x17
libc.free + 0xa3
tds_free_column + 0x24
imd.tds_free_results + 0x85
tds_free_all_results + 0x15
imd.tds_submit_query + 0x6d

All this is running on gentoo linux gcc 2.95x connecting to MS SQL Server 
2000 
on Windows 2000.

here's an ldd on my program:
mark@mark imd $ ldd imd
        libdl.so.2 => /lib/libdl.so.2 (0x4002b000)
        libm.so.6 => /lib/libm.so.6 (0x4002f000)
        libpthread.so.0 => /lib/libpthread.so.0 (0x40051000)
        libc.so.6 => /lib/libc.so.6 (0x40067000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)


I have verified that the parameters I'm passing to tds_submit_query are valid:
The TDSSOCKET is correct. The query is also valid, that is it is quite short 
and null terminated. The TDSSOCKET, interestingly enough, gets hosed after 
the sigsegv. All the data in the TDSSOCKET structure is altered 
significantly.

./configure --eneable-threadsafe --tdsver=7.0

is how I configured it.


Thanks,

Mark