How to decode a PERL core

[Enrico Venturi]

Hello again
I understood that a PERL program can dump...
I tried to decode the dump by the gdb, backtrace, but I had very few informations, namely:
(gdb) bt
#0 0x402cc in Perl_newSVpvf+0xc ()
#1 0x6b0d8 in Perl_pp_padav+0x108 ()
#2 0x63360 in Perl_newHVhv+0x78 ()

The core seems to contain a lot of informations... How can I get them?

[H.Merijn Brand (procura]

Only those three?

These are from the perl run engine's very innards, and won't tell you much about what function(ality) is failing.

please provide more stack entries

FWIW this is the code that is dealing with adding a value/entry to a (anonymous) hash or stash

Enjoy, Have FUN! H.Merijn

[Muthukumar_5]

We can get each and every frame information as,

gdb> info f

IS your core full one??

Try to make ulimit -c unlimited and get the core again and analyse it.

To analyse the frame's of
(gdb) bt
#0 0x402cc in Perl_newSVpvf+0xc ()
#1 0x6b0d8 in Perl_pp_padav+0x108 ()
#2 0x63360 in Perl_newHVhv+0x78 ()

(gdb) info frame 0

It will give some more informataions.

I hope the problem is over Perl_newHVhv+0x78 () location

[Enrico Venturi]

Sorry,
I used the wrong PERL interpreter ...

This is the actual (I hope) stack trace

(gdb) bt
#0 0x402cc in Perl_sv_newmortal+0x14 ()
#1 0x6b2d8 in refto+0x90 ()
#2 0x6b0d8 in Perl_pp_srefgen+0x18 ()
#3 0x633ac in Perl_runops_standard+0x3c ()
#4 0x1d628 in perl_run+0x358 ()
#5 0x1afb8 in main+0x80 ()
(gdb)