> Thanks for your reply Jenda.
>
> There isn't any explicit signal handling code being used.
> Are you suggesting there is something going on between
> the driver and the DBI module?
No, rather than something probably totally unrelated to DBI assigned
something to %SIG{__DIE__}. Maybe in a module where you would not
expect any such meddling with %SIG.
Are you sure you have the same versions of all modules on both
machines?
This prints the versions of all loaded modules:
{
no strict 'refs';
foreach (sort keys %INC) {
next unless m{^(.*)\.pm$};
(my $mod = $1) =~ s{[\\/]+}{::}g;
print "$mod : ${$mod . '::VERSION'}\n"
}
}
Though the traces suggest that it is not the case, but rather
something spicy going on inside DBD::ORACLE.
Sorry, can't help with that, Jenda
===== [email protected] === http://Jenda.Krynicky.cz =====
When it comes to wine, women and song, wizards are allowed
to get drunk and croon as much as they like.
-- Terry Pratchett in Sourcery
