Re^3: stack trace from thread exit

ig was responding to my request. Because I suspect XSUB C functions, I was looking to get a gdb bt; and here it is:

Thread 2 (Thread 25070):
#0  0x0000000000446c34 in Perl_hv_common ()
No symbol table info available.
#1  0x0000000000447fee in Perl_hv_common_key_len ()
No symbol table info available.
#2  0x00000000004d3b3f in Perl_gv_fetchmeth ()
No symbol table info available.
#3  0x00000000004d3d32 in Perl_gv_fetchmeth ()
No symbol table info available.
#4  0x00000000004d5dae in Perl_Gv_AMupdate ()
No symbol table info available.
#5  0x00000000004613cb in Perl_sv_bless ()
No symbol table info available.
#6  0x0000000000461836 in Perl_newSVrv ()
No symbol table info available.
#7  0x0000000000468ff6 in Perl_sv_setref_pv ()
No symbol table info available.
#8  0x00007f6c0548b63e in XS_Net__SSH2__new () from /auto/share/perl/5
+.8.9/lib/site_perl/5.8.9/x86_64-linux-thread-multi/auto/Net/SSH2/SSH2
+.so
No symbol table info available.
#9  0x00000000004547fb in Perl_pp_entersub ()
No symbol table info available.
#10 0x0000000000452d06 in Perl_runops_standard ()
No symbol table info available.
#11 0x00000000004507ce in Perl_call_sv ()
No symbol table info available.
#12 0x00007f6c05aab899 in S_ithread_run () from /auto/share/perl/5.8.9
+/lib/5.8.9/x86_64-linux-thread-multi/auto/threads/threads.so
No symbol table info available.
#13 0x00007f6c0664e9ca in start_thread () from /lib/libpthread.so.0
No symbol table info available.
#14 0x00007f6c063ab6fd in clone () from /lib/libc.so.6
No symbol table info available.
#15 0x0000000000000000 in ?? ()
No symbol table info available.
[download]

I'm not sure what to make of it yet.

Comment on Re^3: stack trace from thread exit Download Code

Replies are listed 'Best First'.
Re^4: stack trace from thread exit by ig (Vicar) on Oct 26, 2010 at 01:37 UTC
If you compile perl and your XS code with -g flag, gdb will be able to show you more information, including where and in which file each frame in the stack relates to. See Building a debugging perl in the INSTALL file that comes with the perl source for guidance on how to do this for perl. This will make it easier to understand, but nothing will make it easy - between perl, XS, SSH and threads, you have quite a complicated situation.	[reply]

Replies are listed 'Best First'.

Re^4: stack trace from thread exit
by ig (Vicar) on Oct 26, 2010 at 01:37 UTC

If you compile perl and your XS code with -g flag, gdb will be able to show you more information, including where and in which file each frame in the stack relates to.

See Building a debugging perl in the INSTALL file that comes with the perl source for guidance on how to do this for perl.

This will make it easier to understand, but nothing will make it easy - between perl, XS, SSH and threads, you have quite a complicated situation.

[reply]