On 21/4/2012 11:35 πμ, Nikolaos Milas wrote: > Program received signal SIGPIPE, Broken pipe. > 0x000000372ac0df15 in send () from /lib64/libpthread.so.0
On one of these events, I did: (gdb) backtrace #0 0x000000372ac0df15 in send () from /lib64/libpthread.so.0 #1 0x000000372c0cf063 in Perl_pp_send () from /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so #2 0x000000372c08a39e in Perl_runops_standard () from /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so #3 0x000000372c0380ba in perl_run () from /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so #4 0x00000000004017bc in main () and: (gdb) backtrace full #0 0x000000372ac0df15 in send () from /lib64/libpthread.so.0 No symbol table info available. #1 0x000000372c0cf063 in Perl_pp_send () from /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so No symbol table info available. #2 0x000000372c08a39e in Perl_runops_standard () from /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so No symbol table info available. #3 0x000000372c0380ba in perl_run () from /usr/lib64/perl5/5.8.8/x86_64-linux-thread-multi/CORE/libperl.so No symbol table info available. #4 0x00000000004017bc in main () No symbol table info available. Please help in resolving this issue. I can follow any other debugging directions/suggestions. Thanks, Nick ------------------------------------------------------------------------------ For Developers, A Lot Can Happen In A Second. Boundary is the first to Know...and Tell You. Monitor Your Applications in Ultra-Fine Resolution. Try it FREE! http://p.sf.net/sfu/Boundary-d2dvs2 _______________________________________________ Nfsen-discuss mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/nfsen-discuss
