debconf-communicate crashed with SIGSEGV in Perl_pp_leavesub()

Bug #666070 reported by krzysztof kowalczyk
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
perl (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: debconf

new to linux. error appeared while installing ubuntu

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: debconf 1.5.28ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic i686
Architecture: i386
Date: Sun Oct 24 17:51:38 2010
ExecutablePath: /usr/bin/debconf-communicate
InterpreterPath: /usr/bin/perl
LiveMediaBuild: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
PackageArchitecture: all
ProcCmdline: /usr/bin/perl -w /usr/bin/debconf-communicate -fnoninteractive ubiquity
ProcEnviron:
 LANGUAGE=
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x80d6ec6 <Perl_pp_leavesub+630>: add %al,-0x74cbb975(%eax)
 PC (0x080d6ec6) ok
 source "%al" ok
 destination "-0x74cbb975(%eax)" (0x9341b54b) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: debconf
StacktraceTop:
 Perl_pp_leavesub ()
 perl_run ()
 main ()
Title: debconf-communicate crashed with SIGSEGV in Perl_pp_leavesub()
UserGroups:

Revision history for this message
krzysztof kowalczyk (puggydad) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 Perl_pp_leavesub ()
 perl_run ()
 main ()

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 debconf (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Colin Watson (cjwatson)
affects: debconf (Ubuntu) → perl (Ubuntu)
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

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

Other bug subscribers

Remote bug watches

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