perl crashed with SIGSEGV in Perl_mg_free()

Bug #678060 reported by Volodymyr Kolesnykov
16
This bug affects 1 person
Affects Status Importance Assigned to Milestone
perl (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: perl

Could be a duplicate of the Bug #604437; differences are Ubuntu releases (10.04 and 10.10) and perl versions.

vladimir@hvosting:~$ lsb_release -rd
Description: Ubuntu 10.10
Release: 10.10
vladimir@hvosting:~$ apt-cache policy perl
perl:
  Installed: 5.10.1-12ubuntu2
  Candidate: 5.10.1-12ubuntu2
  Version table:
 *** 5.10.1-12ubuntu2 0
        500 http://ua.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: perl-base 5.10.1-12ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-23.37-server 2.6.35.7
Uname: Linux 2.6.35-23-server x86_64
Architecture: amd64
Date: Sun Nov 21 10:25:11 2010
ExecutablePath: /usr/bin/perl
ProcCmdline: /usr/sbin/munin-node\ [127.0.0.1]
ProcEnviron:

SegvAnalysis:
 Segfault happened at: 0x7fde1e4ef284 <Perl_mg_free+84>: mov 0x8(%rbx),%rax
 PC (0x7fde1e4ef284) ok
 source "0x8(%rbx)" (0x04000008) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: perl
StacktraceTop:
 Perl_mg_free () from /usr/lib/libperl.so.5.10
 Perl_sv_clear () from /usr/lib/libperl.so.5.10
 Perl_sv_free2 () from /usr/lib/libperl.so.5.10
 Perl_hv_free_ent () from /usr/lib/libperl.so.5.10
 ?? () from /usr/lib/libperl.so.5.10
Title: perl crashed with SIGSEGV in Perl_mg_free()
UserGroups:

Revision history for this message
Volodymyr Kolesnykov (sjinks) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 Perl_mg_free () from /usr/lib/libperl.so.5.10
 Perl_sv_clear () from /usr/lib/libperl.so.5.10
 Perl_sv_free2 () from /usr/lib/libperl.so.5.10
 Perl_hv_free_ent () from /usr/lib/libperl.so.5.10
 ?? () from /usr/lib/libperl.so.5.10

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in perl (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
Brian Murray (brian-murray) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Looking at the bugs you've reported (and the lack of other bugs like this being reported) it seems quite likely that there is something going on with your installation or hardware. Please run a memory test on your system to ensure that there are no hardware errors with your memory.

In the event that there are no memory errors please add the output from 'cat /proc/cpuinfo' and your '/var/log/dmesg' file to one of your bug reports. If you do discover that your memory is bad please set this bug's status to Invalid. Thanks in advance and good luck!

Changed in perl (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for perl (Ubuntu) because there has been no activity for 60 days.]

Changed in perl (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.