Re: bsqldb SEGFAULT abend

Hi James,

I initially run the same test and the results were OK. Then I tried to
specify a different COLSEP and got SEGFAULT, session log follows.

PS: I replaced freetds 0.82 bsqldb.c with the rev 1.39 source and run
configure/make.

Thanks,

Ronildo
____________________________________________________________________________
______________

[aum@ctmserver ~]$ valgrind bsqldb -S aumdomain -U aum -P xxxxxx -D ctm -t ^
==24665== Memcheck, a memory error detector
==24665== Copyright (C) 2002-2009, and GNU GPL'd, by Julian Seward et al.
==24665== Using Valgrind-3.5.0 and LibVEX; rerun with -h for copyright info
==24665== Command: bsqldb -S aumdomain -U aum -P xxxxxx -D ctm -t ^
==24665==
select CMD_LINE from BSQLDB_TEST;
go
CMD_LINE
----------------------------------------------------------------------------
----------------------------------------------------------------------------
----------------------------------------------------------------------------
----------------------------
==24665== Invalid read of size 1
==24665==    at 0x4006848: strlen (mc_replace_strmem.c:275)
==24665==    by 0xB241E8: vfprintf (in /lib/libc-2.7.so)
==24665==    by 0xB29971: fprintf (in /lib/libc-2.7.so)
==24665==    by 0x804B1B7: main (bsqldb.c:544)
==24665==  Address 0x1 is not stack'd, malloc'd or (recently) free'd
==24665==
==24665==
==24665== Process terminating with default action of signal 11 (SIGSEGV)
==24665==  Access not within mapped region at address 0x1
==24665==    at 0x4006848: strlen (mc_replace_strmem.c:275)
==24665==    by 0xB241E8: vfprintf (in /lib/libc-2.7.so)
==24665==    by 0xB29971: fprintf (in /lib/libc-2.7.so)
==24665==    by 0x804B1B7: main (bsqldb.c:544)
==24665==  If you believe this happened as a result of a stack
==24665==  overflow in your program's main thread (unlikely but
==24665==  possible), you can try to increase the size of the
==24665==  main thread stack using the --main-stacksize= flag.
==24665==  The main thread stack size used in this run was 10485760.
ctmcontb -DELETEFROM "*" $1 $2==24665==
==24665== HEAP SUMMARY:
==24665==     in use at exit: 224,501 bytes in 72 blocks
==24665==   total heap usage: 218 allocs, 146 frees, 366,309 bytes allocated
==24665==
==24665== LEAK SUMMARY:
==24665==    definitely lost: 4 bytes in 1 blocks
==24665==    indirectly lost: 177 bytes in 7 blocks
==24665==      possibly lost: 0 bytes in 0 blocks
==24665==    still reachable: 224,320 bytes in 64 blocks
==24665==         suppressed: 0 bytes in 0 blocks
==24665== Rerun with --leak-check=full to see details of leaked memory
==24665==
==24665== For counts of detected and suppressed errors, rerun with: -v
==24665== ERROR SUMMARY: 1 errors from 1 contexts (suppressed: 22 from 10)
Segmentation Fault <-------- this line translated from portuguese
[aum@ctmserver ~]$
____________________________________________________________________________
______________

-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of James K. Lowden
Sent: sábado, 3 de abril de 2010 13:10
To: FreeTDS Development Group
Subject: Re: [freetds] bsqldb SEGFAULT abend

James K. Lowden wrote:
> 
> If you changed your SQL to convert the column to varchar, your memory 
> error will go away.  I'll look to add proper SYBTEXT handling.  No 
> reason it can't be made to work.

Committed TEXT support for bsqldb to CVS HEAD, revision 1.39.  

Thanks for pointing out these problems.  Let me know if the problem is
solved, please.  

--jkl
_______________________________________________
FreeTDS mailing list
[email protected]
http://lists.ibiblio.org/mailman/listinfo/freetds