PEPPLER.ORG
Michael Peppler
Sybase Consulting
Menu
Home
Sybase on Linux
Install Guide for Sybase on Linux
General Sybase Resources
General Perl Resources
Freeware
Sybperl
Sybase::Simple
DBD::Sybase
BCP Tool
Bug Tracker
Mailing List Archive
Downloads Directory
FAQs
Sybase on Linux FAQ
Sybperl FAQ
Personal
Michael Peppler's resume

sybperl-l Archive

Up    Prev    Next    

From: michael dot x dot peppler at jpmchase dot com
Subject: Re: DBD::Sybase on freetds on Linux crashes given empty string
Date: Mar 27 2009 6:55AM

Hmmm - I suspect that this is a freetds bug.

Here's what I get with OpenClient (under cygwin:)

$ perl test.pl
DBD::Sybase::db do failed: OpenClient message: LAYER = (1) ORIGIN = (1) 
SEVERITY = (1) NUMBER = (136)
Server SYBDEVOL, database
Message String: ct_command(LANG): user api layer: external error: A string 
of length 0 is not allowed for parameter buf.

So OpenClient checks this on input (which makes sense)...

Michael






Ed Avis  
Sent by: owner-sybperl-l@peppler.org
03/26/2009 07:13 PM

To
sybperl-l@peppler.org
cc

Subject
DBD::Sybase on freetds on Linux crashes given empty string






I have DBD::Sybase 1.09 and freetds 0.82 on Fedora Linux 10.  I find that 
trying
to execute an empty SQL string crashes, for example

    use DBI;
    use DBD::Sybase;
    my $dbh
      = DBI->connect("dbi:Sybase:MY_SERVER", 'username', 'password');
    $dbh->do('');

produces some output like

*** glibc detected *** perl: free(): invalid next size (fast): 0x08f472d8 
***
======= Backtrace: =========
/lib/libc.so.6[0x19a3a4]
/lib/libc.so.6(cfree+0x96)[0x19c356]
/usr/lib/perl5/5.10.0/i386-linux-thread-multi/CORE/libperl.so
(truncated)

Can anyone else reproduce this?  Is the bug likely to be in freetds or in
DBD::Sybase?

-- 
Ed Avis 




-----------------------------------------
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.

This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.

Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to UK legal entities.