Subject: | Crash of DBD::Firefox on Windows 7 64 |
Date: | Tue, 16 Dec 2014 19:04:06 +0100 |
To: | bug-DBD-Firebird [...] rt.cpan.org |
From: | Raphael Crochet <raphael.crochet [...] actia.fr> |
Hi,
I have the same crash than
https://rt.cpan.org/Public/Bug/Display.html?id=99309
Crash rises at DBI->Connect.
Configuration
Windows 7 64 bits
Strawberry Perl 5.18.4.1, 64 bits
Firebird 2.5.3, 64 bits
DBI 1.6.3.2
DBD:: Firebird 1.17
I added some code to understand behaviour.
Here is a chunk of code.
my
$db_mea="D:/comm/mesure/AnCoRe/depots/measure_data_str64perl/data/outputV2/MEASURE.FDB";
if ( not open (OUTPUTFILE, ">$OutputFile") ) {
die "unable to open file $OutputFile";
}
if ( not open (INPUTFILE, "<$db_mea") ) {
die "unable to open file $db_mea";
}
close (INPUTFILE);
#------------------------------------------------------------------------------
print "MakeJoinTable:begin GMT ".gmtime()."\n";
print "database name: $db_mea \n";
DBI->trace(15, "raf_dbitrace.txt");
my @driver_names = DBI->available_drivers;
my $dbh_mea = DBI->connect("dbi:Firebird:dbname=$db_mea");
There is no error with available_drivers: DBI is still OK. The connect is
fatal.
I put the DBI trace file I got in annex.
I'm not sure to understand all, but Firebird seems to load. The login fail
and didn't end. I'll make some other tests around that.
I looked at the DBD::Firebird.
In the dbdimp.c file I saw the DBI_TRACE_imp_xxh macro. I suppose
str64perl\perl\site\lib\auto\DBD\Firebird\firebird.dll is able to log some
trace but I don't know yet how to activate it.
I guess I'll have to compile with NO_TRACE_MSGS undefined. I am not sure to
get enough courage to do this (I'll have to motivate myself).
I would be very grateful to get a little help to overcome this crash.
In the past, I managed to compile the DBD::Interbase driver and it was a
real pain. But it was worth it: I used it for many years with ActiveState
in 32 bits.
I hope it will be the same with DBD::Firebird and Strawberry 64, even if it
is a little tricky :-)
Regards
Raphaƫl CROCHET
Message body is not shown because sender requested not to inline it.