Dear Andrew,

When you want help, listen to those providing it.

I said "[EMAIL PROTECTED]" - not dbi-dev.

However, given the volume of output, maybe it is just as well.  Fewer people
got the overload of email.  We needed to know what the error was -- we can't
guess at what your trouble was.  But we really didn't need each of the test
lines.

On Thu, Jul 31, 2008 at 12:46 AM, Kekkos, Andrew <
[EMAIL PROTECTED]> wrote:

>
>
> [EMAIL PROTECTED] root]#       perl -V
> Summary of my perl5 (revision 5.0 version 8 subversion 0) configuration:
>

5.8.0 was released in 2002; 5.8.8 was released in 2006; 5.10.0 was released
in December 2007.

Thanks for the Perl -V output...


When you get to the relevant places, you find that the problem is in the
t*_85gofer.t tests - and looks like:


t/zvp_85gofer.............ok 78/0Error thawing: panic: realloc, at
/var/tmp/.cpan/build/DBI-1.605/blib/lib/DBI/Gofer/Serializer/Storable.pm
line 56 (data='GoFER1:....DBI::Gofer::Response.................'), pid 14288
stack trace follows: at
/var/tmp/.cpan/build/DBI-1.605/blib/lib/DBI/Gofer/Transport/Base.pm line 98

      
DBI::Gofer::Transport::Base::_thaw_data('DBD::Gofer::Transport::pipeone=HASH(0x139aae0)','GoFER1:\x{5}\x{6}\x{11}\x{14}DBI::Gofer::Response\x{3}\x{0}\x{0}\x{0}\x{8}\x{4}\x{2}\x{0}\x{0}\x{0}\x{1}\x{8}\x{c2}\x{81}\x{0}\x{0}\x{0}\x{2}rv\x{5}\x{0}\x{0}\x{0}\x{6}errst...')
called at /var/tmp/.cpan/build/DBI-1.605/blib/lib/DBD/Gofer/Transport/
pipeone.pm line 194

      
DBD::Gofer::Transport::pipeone::receive_response_by_transport('DBD::Gofer::Transport::pipeone=HASH(0x139aae0)','DBI::Gofer::Request=HASH(0x139b980)')
called at
/var/tmp/.cpan/build/DBI-1.605/blib/lib/DBD/Gofer/Transport/Base.pm line 141

      eval {...} called at
/var/tmp/.cpan/build/DBI-1.605/blib/lib/DBD/Gofer/Transport/Base.pm line 139

      DBD::Gofer::Transport::Base::__ANON__() called at
/var/tmp/.cpan/build/DBI-1.605/blib/lib/DBD/Gofer/Transport/Base.pm line 155

      
DBD::Gofer::Transport::Base::receive_response('DBD::Gofer::Transport::pipeone=HASH(0x139aae0)','DBI::Gofer::Request=HASH(0x139b980)','CODE(0x139ba70)')
called at /var/tmp/.cpan/build/DBI-1.605/blib/lib/DBD/Gofer.pm line 295

      DBD::Gofer::db::go_dbh_method('DBI::db=HASH(0x139b790)','undef','ping')
called at DBI::PurePerl DBI::db::go_dbh_method line 42

      DBI::__ANON__('DBI::db=HASH(0x1386610)','undef','ping') called at
/var/tmp/.cpan/build/DBI-1.605/blib/lib/DBD/Gofer.pm line 238


DBD::Gofer::dr::connect('DBI::dr=HASH(0x8f2760)','transport=pipeone;policy=pedantic;perl=/usr/bin/perl
-Mblib=...','undef','undef','HASH(0x13873a0)') called at DBI::PurePerl
DBI::dr::connect line 48


DBI::__ANON__('DBI::dr=HASH(0x8749e0)','transport=pipeone;policy=pedantic;perl=/usr/bin/perl
-Mblib=...','undef','undef','HASH(0x13873a0)') called at
/var/tmp/.cpan/build/DBI-1.605/blib/lib/DBI.pm line 638

      DBI::__ANON__('undef','undef') called at
/var/tmp/.cpan/build/DBI-1.605/blib/lib/DBI.pm line 706

      
DBI::connect('DBI','dbi:Gofer:transport=pipeone;policy=pedantic;perl=/usr/bin/per...','undef','undef','HASH(0x13787c0)')
called at ./t/85gofer.t line 145

      main::run_tests('pipeone','HASH(0x7755f0)','pedantic') called at
./t/85gofer.t line 103

      eval {...} called at ./t/85gofer.t line 103

      require ./t/85gofer.t called at t/zvp_85gofer.t line 3



#   Failed test 'pipeone: DBI
connect('transport=pipeone;policy=pedantic;perl=/usr/bin/perl
-Mblib=/var/tmp/.cpan/build/DBI-1.605/blib;timeout=60;dsn=dbi:DBM:dbm_type=SDBM_File;lockfile=0','',...)
failed: Error thawing: panic: realloc, at
/var/tmp/.cpan/build/DBI-1.605/blib/lib/DBI/Gofer/Serializer/Storable.pm
line 56 (data='GoFER1:....DBI::Gofer::Response.................') at
/var/tmp/.cpan/build/DBI-1.605/blib/lib/DBI/Gofer/Transport/Base.pm line 99.
at ./t/85gofer.t line 145

# '

#   at ./t/85gofer.t line 104.


There's a memory management problem - clearly.

Equally, I am far from convinced anyone is going to be interested in
debugging this problem for an archaic version of Perl (especially since the
problem almost certainly does not reproduce in the current version.

My strong recommendation would be to upgrade to Perl 5.10.0; failing that,
upgrade to 5.8.8.

You may get lucky and someone may be prepared to help with your actual
configuration, but I have serious doubts.


-- 
Jonathan Leffler <[EMAIL PROTECTED]> #include <disclaimer.h>
Guardian of DBD::Informix - v2008.0513 - http://dbi.perl.org
"Blessed are we who can laugh at ourselves, for we shall never cease to be
amused."

Reply via email to