fontforge crashed with SIGSEGV in SCNumberPoints()

Bug #179281 reported by Samuel Lidén Borell
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fontforge (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: fontforge

It crashed when I tried to generate instructions (Hints->AutoInstr->Nowakowski) on the Bitstream Vera Sans font (included in Ubuntu).

I'm using a pre-release version of Hardy (updated 2007-12-28).

ProblemType: Crash
Architecture: amd64
Date: Sat Dec 29 21:23:51 2007
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/fontforge
NonfreeKernelModules: cdrom
Package: fontforge 0.0.20071002-1
PackageArchitecture: amd64
ProcCmdline: /usr/bin/fontforge
ProcCwd: /home/samuellb
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: fontforge
StacktraceTop:
 ?? () from /usr/lib/fontforge/libfontforge.so.1
 ?? () from /usr/lib/fontforge/libfontforge.so.1
 SCNumberPoints ()
 NowakowskiSCAutoInstr ()
 ?? () from /usr/lib/fontforge/libfontforge.so.1
Title: fontforge crashed with SIGSEGV in SCNumberPoints()
Uname: Linux dv5000 2.6.22-14-generic #1 SMP Sun Oct 14 21:45:15 GMT 2007 x86_64 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video
SegvAnalysis:
 Segfault happened at: 0x2ba6b4f4330a: mov 0x10(%rax),%rbx
 PC (0x2ba6b4f4330a) ok
 source "0x10(%rax)" (0x00000010) not located in a known VMA region (needed readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA

Tags: apport-crash
Revision history for this message
Samuel Lidén Borell (samuellb) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:_SCRefNumberPoints2 (_rss=0x7ffff61cac80, sc=0x90e210, pnum=30)
_SCRefNumberPoints2 (_rss=0x7ffff61cac80, sc=0x915ad0, pnum=25)
SCNumberPoints (sc=<value optimized out>) at charview.c:3072
NowakowskiSCAutoInstr (gic=0x7ffff61cada0, sc=0x97e790)
FVAutoInstr (fv=0x78cb00, usenowak=1) at fontview.c:5727

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in fontforge:
importance: Undecided → Medium
Revision history for this message
Samuel Lidén Borell (samuellb) wrote :

It seems that the upgrade to Hardy didn't work as it should (probably because I was using a mirrored archive which didn't have the Hardy packages). So this might actually have happened with a version of font-forge from Ubuntu 7.10 .

Revision history for this message
Samuel Lidén Borell (samuellb) wrote :

It's reproducable under 8.04 from 2007-12-29

Kees Cook (kees)
description: updated
Revision history for this message
Vanessa Lee (vanessax) wrote :

The same function crashes intermittently on Lucid.

Changed in fontforge (Ubuntu):
status: New → Confirmed
Revision history for this message
dino99 (9d9) wrote :

That version has died long ago; no more supported

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