Skip Menu |

This queue is for tickets about the DBD-SQLite CPAN distribution.

Report information
The Basics
Id: 1843
Status: resolved
Priority: 0/
Queue: DBD-SQLite

Owner: Nobody in particular
Requestors: mark [...]

Bug Information
Severity: Normal
Broken in: 0.21
Fixed in: 0.21

Subject: SELECT after rollback causes segmentation fault
Download (untitled) / with headers
text/plain 3.5k
I found that this code causes a segmentation fault at the SELECT rater than simply giving a "no such table" error: #!/usr/bin/perl use strict; use warnings; unlink "foo.db"; use DBI; my $dbh = DBI->connect("dbi:SQLite:foo.db", "", "", { AutoCommit => 0 } ); # just do the SQL needed to create a table $dbh->do(q{ CREATE TABLE modules (day INTEGER PRIMARY KEY, name TEXT, maintainer TEXT) }); my $sth = $dbh->prepare(q{ INSERT INTO modules (name, maintainer) VALUES (?,?) }); # run that insert, with the text to replace the ? with $sth->execute("URI::Find", "ROSCH"); $sth->execute("IO::AtomicFile","ERYQ"); $sth->execute("DBD::SQLite", "MSERGEANT"); $dbh->rollback; # find which day baud's modules are shown on my $sth2 = $dbh->prepare(q{ SELECT day, name FROM modules WHERE maintainer = ? }); $sth2->execute("MSERGEANT"); I'm running standard debain i386 unstable perl, the details I shall now include: Summary of my perl5 (revision 5.0 version 8 subversion 0) configuration: Platform: osname=linux, osvers=2.4.19, archname=i386-linux-thread-multi uname='linux cyberhq 2.4.19 #1 smp sun aug 4 11:30:45 pdt 2002 i686 unknown unknown gnulinux ' config_args='-Dusethreads -Duselargefiles -Dccflags=-DDEBIAN -Dcccdlflags=-fPIC -Darchname=i386-linux -Dprefix=/usr -Dprivlib=/usr/share/perl/5.8.0 -Darchlib=/usr/lib/perl/5.8.0 -Dvendorprefix=/usr -Dvendorlib=/usr/share/perl5 -Dvendorarch=/usr/lib/perl5 -Dsiteprefix=/usr/local -Dsitelib=/usr/local/share/perl/5.8.0 -Dsitearch=/usr/local/lib/perl/5.8.0 -Dman1dir=/usr/share/man/man1 -Dman3dir=/usr/share/man/man3 -Dman1ext=1 -Dman3ext=3perl -Dpager=/usr/bin/sensible-pager -Uafs -Ud_csh -Uusesfio -Uusenm -Duseshrplib -Dd_dosuid -des' hint=recommended, useposix=true, d_sigaction=define usethreads=define use5005threads=undef useithreads=define usemultiplicity=define useperlio=define d_sfio=undef uselargefiles=define usesocks=undef use64bitint=undef use64bitall=undef uselongdouble=undef usemymalloc=n, bincompat5005=undef Compiler: cc='cc', ccflags ='-D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fno-strict-aliasing -I/usr/local/include -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64', optimize='-O3', cppflags='-D_REENTRANT -D_GNU_SOURCE -DDEBIAN -fno-strict-aliasing -I/usr/local/include' ccversion='', gccversion='2.95.4 20011002 (Debian prerelease)', gccosandvers='' intsize=4, longsize=4, ptrsize=4, doublesize=8, byteorder=1234 d_longlong=define, longlongsize=8, d_longdbl=define, longdblsize=12 ivtype='long', ivsize=4, nvtype='double', nvsize=8, Off_t='off_t', lseeksize=8 alignbytes=4, prototype=define Linker and Libraries: ld='cc', ldflags =' -L/usr/local/lib' libpth=/usr/local/lib /lib /usr/lib libs=-lgdbm -ldb -ldl -lm -lpthread -lc -lcrypt perllibs=-ldl -lm -lpthread -lc -lcrypt libc=/lib/, so=so, useshrplib=true, gnulibc_version='2.2.5' Dynamic Linking: dlsrc=dl_dlopen.xs, dlext=so, d_dlsymun=undef, ccdlflags='-rdynamic' cccdlflags='-fPIC', lddlflags='-shared -L/usr/local/lib' Characteristics of this binary (from libperl): Compile-time options: MULTIPLICITY USE_ITHREADS USE_LARGE_FILES PERL_IMPLICIT_CONTEXT Built under linux Compiled at Sep 14 2002 17:36:21 @INC: /etc/perl /usr/local/lib/perl/5.8.0 /usr/local/share/perl/5.8.0 /usr/lib/perl5 /usr/share/perl5 /usr/lib/perl/5.8.0 /usr/share/perl/5.8.0 /usr/local/lib/site_perl .
Download (untitled) / with headers
text/plain 350b
Ugh. I can't figure out what's going on here. My guess is it's a small bug in the sqlite library somewhere. It works fine if you do a commit after creating the table (DML statements are transactional in SQLite). Marking resolved because the segfault happens in the sqlite library. If I get around to it I'll post a query about it to the sqlite list.

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to