FreeTDS Development Group

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

> From: Michael Peppler [mailto:mpeppler AT peppler.org]
> Sent: February 10, 2003 4:33 PM
> > > 
> > > I'm running perl 5.8.0 in a Solaris 8 environment, using 
> > > FreeTDS-0.61 and
> > > DBD::Sybase 0.95.  It was recommended that I use the snapshot 
> > > release of
> > > FreeTDS to resolve some issues with compatability.
> > > 
> > > However, when I run a test perl script to connect to the same 
> > > database, perl dumps core.
> 
> I think the problem is in this code from DBD::Sybase:
> 
>     if(imp_dbh->chainedSupported) {
>         CS_BOOL value = CS_FALSE;
> 
>         if(dbis->debug >= 2)
>             PerlIO_printf(DBILOGFP, "    syb_db_login() -> 
> checking for
> chained transactions\n");
>         retcode = ct_options(connection, CS_SET, CS_OPT_CHAINXACTS, 
>                              &value, CS_UNUSED, NULL);
>         if(retcode == CS_FAIL) {
>             imp_dbh->doRealTran = 1;
>             imp_dbh->chainedSupported = 0;
>         }
>         if(dbis->debug >= 2)
>             PerlIO_printf(DBILOGFP, "    syb_db_login() -> chained
> transactions are %s supported\n", retcode == CS_FAIL ? "not" : "");
>     }
> 
> It's the ct_options() call that causes the segfault, apparently.

Ah, well, ct-options returns true as long as you pass valid parameters,
regardless of whether we actually *do* anything.  If we just return CS_FAIL
for now, is that good for you, Michael?  I don't know if I want to get into
a conversation with the server about transaction capabilities. 

Chris, if you set TDSDUMP, you should see "ct_option: UNIMPLEMENTED 7" and
possibly others.  The "7" is CS_OPT_CHAINXACTS.  If I know the set, I can
look into it.  

--jkl


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.