On 18 марта 2009, Werner LEMBERG wrote:
Ian also reported this problem for gcc 4.2.3. Please try a newer gcc
version, say, 4.3.2, which works for me without problems.
I recompiled freetype with gcc-4.3.3 and -O2 -mtune=i686. It does not cause
crashes of ftview.
--
Andrey V. Panov
panov /@/
I recompiled freetype with gcc-4.3.3 and -O2 -mtune=i686. It does
not cause crashes of ftview.
Very good! It seems we can close this case.
Werner
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
Hi,
Recently I don't have sufficient time to track this bug,
but I experienced similar issue:
* ftview crashes in cache module.
* the crash can be avoided by disable -O2 optimization
My platform is Debian GNU/Linux on x86 (Centrino Duo),
gcc is 4.2.3. My backtrace is similar to the bug reported
* ftview crashes in cache module.
* the crash can be avoided by disable -O2 optimization
My platform is Debian GNU/Linux on x86 (Centrino Duo),
gcc is 4.2.3.
Ian also reported this problem for gcc 4.2.3. Please try a newer gcc
version, say, 4.3.2, which works for me without problems.
I did not changed ftoption.h but defined
CPPFLAGS=-DTT_CONFIG_OPTION_BYTECODE_INTERPRETER \
-DFT_CONFIG_OPTION_SUBPIXEL_RENDERING
before running configure.
OK.
freetype2 was configured with ./configure [...] CFLAGS=-O2
-mtune=i686. ftview was patched with ft2demos-2.3.6.diff
On 13 марта 2009, Werner LEMBERG wrote:
Since the upgrade ftview crashes on loading any font. I tried
ftview from ft2demos-2.3.8 linked against freetype-2.3.8 and from
ft2demos-2.3.9 compiled vs freetype-2.3.9.
For me it works just fine, both static and dynamic builds. Please
give more
It seems to be caused by gcc option -mtune=i686 for libfreetype
compilation, without it ftview does not crash. In both cases I
combined it with -O2. I compiled freetype on slackware 12.2 (x86
linux, gcc 4.2.4). The backtrace of ftview is:
#0 0xb8062a0a in ftc_basic_family_load_bitmap
Hi,
This seems to be a regression in freetype CVS (patented hinting is enabled):
(gdb) run ppem /usr/share/fonts/windows/tahomabd.ttf
Starting program: /packages/ft2demos/bin/.libs/ftview
ppem /usr/share/fonts/windows/tahomabd.ttf
Program received signal SIGSEGV, Segmentation fault.
On Monday 11 June 2007 23:26:50 Ismail Dönmez wrote:
Hi,
This seems to be a regression in freetype CVS (patented hinting is
enabled):
Actually not just tahoma but any TTF font from Windows behaves the same.
Regards,
ismail
--
Perfect is the enemy of good
signature.asc
Description: This
I'm on it at this very moment. seems rendering of patented hinting is garbled
- David
On Mon, 11 Jun 2007 23:26:50 +0300, Ismail Dönmez [EMAIL PROTECTED] said:
Hi,
This seems to be a regression in freetype CVS (patented hinting is
enabled):
(gdb) run ppem
This seems to be a regression in freetype CVS (patented hinting is
enabled):
(gdb) run ppem /usr/share/fonts/windows/tahomabd.ttf
Starting program: /packages/ft2demos/bin/.libs/ftview
ppem /usr/share/fonts/windows/tahomabd.ttf
Program received signal SIGSEGV, Segmentation fault.
11 matches
Mail list logo