http://qs1969.pair.com?node_id=542228


in reply to Core dump when runing "make test" or "perl test.pl"

For those occassions, the best aproach is to have a perl compiled with debugging information.

To do that, download the perl source from some CPAN mirror (get the same version you have on your machine), and run Configure accepting the defaults to the questions asked except for the two below that set the optimization flags and the place where you want this perl installed:

$ tar xzf perl-5.6.1 $ cd perl-5.6.1 $ ./Configure ... What optimizer/debugger flag should be used? [-O2] -g -O0 ... Installation prefix to use? (~name ok) [/usr/local] /usr/local/perl/de +bug/ Directory /usr/local/perl/debug/ doesn't exist. Use that name anyway? + [n] y ... $ make && make test $ su -c "make install" ...
Then recompile the module using this perl:
$ /usr/local/perl/debug/bin/perl Makefile.PL $ make
Now you can run perl and the test script inside the (system) debugger and get meaningful information:
$ gdb /usr/local/perl/debug/bin/perl ... (gdb) r -Mblib t/test.pl ... # the segmentation fault signal will be cought # by the debugger. To see where it happened # run the backtrace command: (gdb) bt ...
and at this point you can try to resolve the bug yourself, or send a bug report containing the backtrace to the module author.