inkscape crashed with SIGSEGV in strlen()

Bug #413610 reported by Emmanuel Pacaud
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
inkscape (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: inkscape

I've just seen this bug report after a reboot. I remember an inkscape crash, but not why or when it did.

ProblemType: Crash
Architecture: i386
Date: Wed Aug 12 19:11:41 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/inkscape
Package: inkscape 0.47~pre1-0ubuntu1
ProcCmdline: inkscape /home/username/Desktop/sortie.pdf
ProcEnviron:
 LANGUAGE=fr_FR.UTF-8
 PATH=(custom, user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
SegvAnalysis:
 Segfault happened at: 0x6976ffb <strlen+11>: cmp %ch,(%eax)
 PC (0x06976ffb) ok
 source "%ch" ok
 destination "(%eax)" (0x7273752f) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: inkscape
StacktraceTop:
 strlen () from /lib/tls/i686/cmov/libc.so.6
 GlobalParams::scanEncodingDirs() ()
 GlobalParams::GlobalParams(char const*) ()
 ?? ()
 ?? ()
Title: inkscape crashed with SIGSEGV in strlen()
Uname: Linux 2.6.31-5-generic i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev pulse-access sambashare scanner vboxusers video

Revision history for this message
Emmanuel Pacaud (emmanuel-pacaud) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:strlen () at ../sysdeps/i386/i486/strlen.S:40
GlobalParams::scanEncodingDirs (this=0x8df8868)
GlobalParams (this=0x8df8868, customPopplerDataDir=0x0)
Inkscape::Extension::Internal::PdfInput::open (
Inkscape::Extension::Input::open (this=0x8d01de8,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in inkscape (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Bryce Harrington (bryce)
visibility: private → public
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.