The attached font crashes when trying to load it.
I'm also attaching gdb backtrace.
Albert
#0 0x7f0fd26b3afe in cff_parse_real (
start=0x7f0fd87681b4
"\177\006\036�ccc\177\f\t\036\021:3o\n\036\022\n\206�\v\036\020\nD_\036\022�\220\231\237\f\f\036\022\n\206�\036\022\212C\1
> The attached font crashes when trying to load it.
Neither 2.3.7 nor the current CVS does crash for me. I tested with
both ftview and ftstring; valgrind doesn't report an error either.
Werner
___
Freetype-devel mailing list
Freetype-devel@nongn
A Diumenge 17 Agost 2008, Werner LEMBERG va escriure:
> > The attached font crashes when trying to load it.
>
> Neither 2.3.7 nor the current CVS does crash for me. I tested with
> both ftview and ftstring; valgrind doesn't report an error either.
Strange, any idea what could be the culprit? I ha
> Strange, any idea what could be the culprit? I have 2.3.5 working and 2.3.7
> failing with "Floating point exception"
>
> Can it be gcc? optimization flags? Something else?
`Floating point exception' probably indicates a compiler bug. Please
try with -O0.
> That is on an amd64 machine are y
A Diumenge 17 Agost 2008, Werner LEMBERG va escriure:
> > Strange, any idea what could be the culprit? I have 2.3.5 working and
> > 2.3.7 failing with "Floating point exception"
> >
> > Can it be gcc? optimization flags? Something else?
>
> `Floating point exception' probably indicates a compiler b
> > `Floating point exception' probably indicates a compiler bug. Please
> > try with -O0.
>
> With -O0 it does not crash, so what now?
What does valgrind say if you compile with -O2? Maybe something isn't
properly initialized in FreeType.
> Do I close the poppler bug and tell the user to go
Albert Astals Cid wrote:
A Diumenge 17 Agost 2008, Werner LEMBERG va escriure:
The attached font crashes when trying to load it.
Neither 2.3.7 nor the current CVS does crash for me. I tested with
both ftview and ftstring; valgrind doesn't report an error either.
Strange, any idea what could
> I don't know if it's the same problem, but I reported a similar
> problem back at the end of July.
>
> See my thread that ends with this post:
>http://lists.gnu.org/archive/html/freetype/2008-07/msg00036.html
> or the bug I filed with Mandriva
>https://qa.mandriva.com/show_bug.cgi?id=42
Werner LEMBERG wrote:
I don't know if it's the same problem, but I reported a similar
problem back at the end of July.
See my thread that ends with this post:
http://lists.gnu.org/archive/html/freetype/2008-07/msg00036.html
or the bug I filed with Mandriva
https://qa.mandriva.com/show_bug.
> Still crashes. See attached for details.
Try to undefine FTC_INLINE in src/cache/ftcmru.h. Does this help?
Werner
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype-devel
Werner LEMBERG wrote:
Still crashes. See attached for details.
Try to undefine FTC_INLINE in src/cache/ftcmru.h. Does this help?
The good news? That works for -O2 (And "-O2 -g"). No crash, no
Valgrind errors.
The bad news? It still crashes for -O3 (And "-O3 -g"). I've
attached a new Va
> > Try to undefine FTC_INLINE in src/cache/ftcmru.h. Does this help?
>
> The good news? That works for -O2 (And "-O2 -g"). No crash, no
> Valgrind errors.
>
> The bad news? It still crashes for -O3 (And "-O3 -g"). I've
> attached a new Valgrind log, but it looks to be virtually identical
>
12 matches
Mail list logo
