The problem is in the debian package not with fontforge itself - I just
removed the debian fontforge and built fontforge from source using
fontforge_full-20110222.tar.bz2. The build from source does not have the
same problem.
The process of making did require pythonui.c which did not register as
Dear Khaled
the segmentation fault is somewhat erratic for example moving around the
letter g does not crash but moving say a character at uf8000 does - in some
cases starting a new font, making it full unicode going to a higher point
and simply pressing element is sufficient to crash. Even if
I use FontForge extensively I never encountered this, and generally it
is less crashy than it used to be. May be it is 64bit specific bug?
Regards,
Khaled
On Thu, Jan 19, 2012 at 05:20:57PM +0800, john knightley wrote:
Dear Khaled
the segmentation fault is somewhat erratic for example
On 01/19/2012 06:15 AM, Khaled Hosny wrote:
I use FontForge extensively I never encountered this, and generally it
is less crashy than it used to be. May be it is 64bit specific bug?
nope. as i've said, i'm able to replicate it in i386.
--dkg
signature.asc
Description: OpenPGP
Also, though this may not be totally relevant, if I get a segfault for any
reason, usually deleting my preferences file in my home directory fixes the
issue. Fofo would segfault on my Mac every time I pressed control in the
glyph window, and this fixed it...
Still, there has to be a problem
Hi fontforge folks--
over on Debian, we've just gotten http://bugs.debian.org/656359, which
appears to contain a reproducible segfault.
Some folks have suggested that it may be due to more recent versions of
dependent libraries, but i haven't been able to track it down in more
detail, i'm
On Thu, Jan 19, 2012 at 01:35:26AM -0500, Daniel Kahn Gillmor wrote:
Hi fontforge folks--
over on Debian, we've just gotten http://bugs.debian.org/656359, which
appears to contain a reproducible segfault.
Some folks have suggested that it may be due to more recent versions of
dependent
On 01/19/2012 02:21 AM, Khaled Hosny wrote:
I can't reproduce this with fontforge built from git master running
under Ubuntu 10.04.
hmm, just trying to build from upstream's git master
(265be01a4ce5978fbb2c1a6ecf6402af0ea54115) with a ./configure make
on sid yields me this error:
cvdgloss.c:
On Thu, Jan 19, 2012 at 02:39:26AM -0500, Daniel Kahn Gillmor wrote:
On 01/19/2012 02:21 AM, Khaled Hosny wrote:
I can't reproduce this with fontforge built from git master running
under Ubuntu 10.04.
hmm, just trying to build from upstream's git master
9 matches
Mail list logo
