pstoedit crashed with SIGSEGV in __longjmp()

Bug #618310 reported by sam tygier
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pstoedit
Unknown
Unknown
pstoedit (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: pstoedit

i get this when i use the extension->render->latex in inkscape.
the equation was:
\(\displaystyle\frac{\pi^2}{6}=\lim_{n \to \infty}\sum_{k=1}^n \frac{1}{k^2}\)

inkscape gave me the feedback:
sh: line 1: 13347 Segmentation fault (core dumped) pstoedit -f plot-svg -dt -ssp "/tmp/inkscape-TYz_gd/eq.ps" "/tmp/inkscape-TYz_gd/eq.svg" > "/tmp/inkscape-TYz_gd/eq.out" 2> "/tmp/inkscape-TYz_gd/eq.err"

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: pstoedit 3.50-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-24.39-generic 2.6.32.15+drm33.5
Uname: Linux 2.6.32-24-generic x86_64
Architecture: amd64
Date: Sun Aug 15 19:02:45 2010
ExecutablePath: /usr/bin/pstoedit
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcCmdline: pstoedit -f plot-svg -dt -ssp /tmp/inkscape-TYz_gd/eq.ps /tmp/inkscape-TYz_gd/eq.svg
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_GB.utf8
SegvAnalysis:
 Segfault happened at: 0x7feebb6a90c8 <__longjmp+72>: jmpq *%rdx
 PC (0x7feebb6a90c8) ok
 source "*%rdx" ok
 SP (0x88ec3f78d50f89e4) not located in a known VMA region (needed readable region)!
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: pstoedit
Stacktrace:
 #0 __longjmp () at ../sysdeps/x86_64/__longjmp.S:56
 No locals.
 #1 0xdb29bf78eae0d4f7 in ?? ()
 No symbol table info available.
 Cannot access memory at address 0x88ec3f78d50f89e4
StacktraceTop:
 __longjmp () at ../sysdeps/x86_64/__longjmp.S:56
 ?? ()
Title: pstoedit crashed with SIGSEGV in __longjmp()
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Revision history for this message
sam tygier (samtygier) wrote :
visibility: private → public
Revision history for this message
sam tygier (samtygier) wrote :

still happens in maverick
(note to get the latex option to show in the menu you need to install pstoedit and texlive-latex-base)

Revision history for this message
sam tygier (samtygier) wrote :
  • eq.ps Edit (96.1 KiB, application/postscript)

i messed with the plugin so that i could get the PS file out. and have attached it.

when i run pstoedit independently of inkscape it still crashes. there seems to be no dbgsym package for pstoedit, so i built it from source, and tried to run it in GDB. i get the error

sam@oberon:/tmp/sam$ gdb /opt/pstoedit/bin/pstoedit
GNU gdb (GDB) 7.1-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /opt/pstoedit/bin/pstoedit...done.
(gdb) run -f plot-svg -dt -ssp eq.ps eq.svg
Starting program: /opt/pstoedit/bin/pstoedit -f plot-svg -dt -ssp eq.ps eq.svg
pstoedit: version 3.50 / DLL interface 108 (build Aug 22 2010 - release build - g++ 4.4.3) : Copyright (C) 1993 - 2009 Wolfgang Glunz
[Thread debugging using libthread_db enabled]
Cannot find new threads: generic error

not sure how to proceed

Revision history for this message
Marcel Stimberg (marcelstimberg) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 616027, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

Changed in pstoedit (Ubuntu):
status: New → Confirmed
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.