Ubuntu
poedit package

poeditor crashed with SIGSEGV

Bug #924350 reported by Dimiter "Arruor" Nikov on 2012-01-31

This bug report is a duplicate of: Bug #907917: Poedit crashes when updating catalog. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	poedit (Ubuntu)	New	Undecided	Unassigned

Bug Description

The program crashes after catalog update, this bug affects me for all 1.4.x versions branch

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: poedit 1.4.6.1-5.1
ProcVersionSignature: Ubuntu 3.2.0-12.20-generic-pae 3.2.2
Uname: Linux 3.2.0-12-generic-pae i686
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: i386
Date: Tue Jan 31 10:44:04 2012
Disassembly: => 0x72: Cannot access memory at address 0x72
ExecutablePath: /usr/bin/poeditor
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: poeditor
SegvAnalysis:
Segfault happened at: 0x72: Cannot access memory at address 0x72
PC (0x00000072) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: poedit
Stacktrace:
#0 0x00000072 in ?? ()
No symbol table info available.
StacktraceTop: ?? ()
Title: poeditor crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio backup cdrom dialout lpadmin plugdev root sambashare vboxusers video www-data

Tags:

Revision history for this message

Dimiter "Arruor" Nikov (arruor) wrote on 2012-01-31:

CoreDump.gz Edit (3.3 MiB, application/x-gzip)
Dependencies.txt Edit (2.8 KiB, text/plain; charset="utf-8")
ProcEnviron.txt Edit (234 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (34.2 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (806 bytes, text/plain; charset="utf-8")
Registers.txt Edit (446 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (1016 bytes, text/plain; charset="utf-8")

visibility:

private → public

Revision history for this message

Apport retracing service (apport) wrote on 2012-01-31:

Stacktrace:
#0 0x00000072 in ?? ()
No symbol table info available.
Backtrace stopped: Not enough registers or memory available to unwind further
StacktraceTop: ?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2012-01-31: ThreadStacktrace.txt