Strap in, this is a bit of a saga...
For DBIx::Threaded testing, I've updated a machine
to Fedora Core 4. Given RedHat's "notoriety" wrt
the Perl they deliver, after installing, I immediately
pull down AS 5.8.7 for Linux and begin testing.
Normal cases work OK, but using threads leads to
bizarre behavior at various times. Since DBIx::Threaded
is behaving nicely on OS X/AS5.8.7 and WinXP/AS5.8.3
(tho WinXP+5.8.3 seem to still have some thread rundown
issues on exit), I decide to build perl 5.8.7 on Fedora 4
from scratch. It builds and installs wo/ problems.
I test DBIx::Threaded w/ DBD::CSV and DBD::SQLite
wo/ any issues. When I start testing DBD::Teradata
(same version which is working very nicely on WinXP and OS X),
it dies very quietly just after connecting. Eventually,
I backtrack to a minimal DBI-only script to debug the issue.
Except there's nothing to debug. On return from
DBD::Teradata::dr::connect, it immediately dies. I trace(),
but there's nothing of note in the logs. I eval{} and
test $@, still nothing.
When I switch to DBI::PurePerl, everything works fine.
So I have to assume that whatever I'm breaking is somewhere in
DBI's connect() finalize code.
Has anyone built perl 5.8.7 on Core 4 and run DBI yet ?
Note that Core 4 uses gcc 4.01; are there any known issues
with that combo I should know about ?
Regards,
Dean Arnold
Presicient Corp.
