On Tue, Feb 17, 2004 at 05:13:09PM -0800, Dianne Yumul wrote: > > >>> print STDERR "Got here 1.3\n"; > > >>> > > >>> my @a = $sth_data->fetchrow_array() or die "fetchrow_array: > > >>> $DBI::errstr\n"; > > >>> > > >>> print STDERR "Got here 1.4\n"; > > > > > Sorry about the lack of version info, we're using DBI-1.40, > > > DBD-Pg-1.31, and PostgreSQL-7.3.5. The query works fine in > > psql. The > > > weird thing is that the program just ends...no error messages, > > > nothing...it's just like there was an exit; buried in > > > fetchrow_array(). Another thing is That this code worked fine with > > > DBI-1.20 and DBD-Pg-1.01. > > > > Try DBI->trace(4) before the fetchrow_array() call. > > Thanks for the tip. After trying DBI->trace(4), I get: > > DBI 1.40-nothread dispatch trace level set to 4 (in pid 15870) > -> fetchrow_array for DBD::Pg::st (DBI::st=HASH(0x854abd8)~0x854ab60) > dbd_st_fetch > dbih_setup_fbav for 9 fields => 0x854ab3c > > Anyone knows what it means?
Seems normal as far as it goes. What's not normal is that the program exits. If that really is the last line of the trace then it exits violently so I suspect you're getting something like a segmentation violation. Try running it using a system tracing tool like truss or strace (you didn't say what kind of system you were using). Tim.
