Skip Menu |

This queue is for tickets about the JavaScript CPAN distribution.

Report information
The Basics
Id: 36497
Status: new
Priority: 0/
Queue: JavaScript

Owner: Nobody in particular
Requestors: CRAKRJACK [...]

Bug Information
Severity: Important
Broken in: 1.07
Fixed in: (no value)

Subject: Using can cause the perl debugger to crash
MIME-Version: 1.0
X-Mailer: MIME-tools 5.426 (Entity 5.426)
Content-Type: text/plain
Charset: utf8
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 1534
Download (untitled) / with headers
text/plain 1.4k
When using, the perl debugger can crash. This appears to happen when the JavaScript context is destroyed. The "Devel::Profile" manpage says, under "Bugs": "Some buggy XS based perl modules can behave erroneously when run under the perl debugger. Since Devel::Profile uses the perl debugger interfaces, these modules will also behave erroneously when being pofiled." I've scoured the net for more information on what bugs/glitches could cause this, but no luck yet... but it looks like running under the debugger may be making perl attempt to double-free an SV? Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 47273699863072 (LWP 13373)] 0x00000033061a1d80 in Perl_sv_clear () from /usr/lib64/perl5/5.8.5/x86_64-linux-thread-multi/CORE/ (gdb) bt #0 0x00000033061a1d80 in Perl_sv_clear () from /usr/lib64/perl5/5.8.5/x86_64-linux-thread-multi/CORE/ #1 0x00000033061a242d in Perl_sv_free () from /usr/lib64/perl5/5.8.5/x86_64-linux-thread-multi/CORE/ #2 0x00000033061c74ec in Perl_free_tmps () from /usr/lib64/perl5/5.8.5/x86_64-linux-thread-multi/CORE/ #3 0x00000033061cf6e9 in Perl_pp_dbstate () from /usr/lib64/perl5/5.8.5/x86_64-linux-thread-multi/CORE/ #4 0x000000330618286a in Perl_runops_debug () from /usr/lib64/perl5/5.8.5/x86_64-linux-thread-multi/CORE/ #5 0x000000330613b5e4 in perl_run () from /usr/lib64/perl5/5.8.5/x86_64-linux-thread-multi/CORE/ #6 0x00000000004019ec in main ()

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to