[hafqa] [hafqa] [Bug 3150] segfault in libfontconfig when using -O0 in application / nokia sans font

From: bugzilla-daemon at maemo.org bugzilla-daemon at maemo.org
Date: Fri Sep 26 16:35:10 EEST 2008
https://bugs.maemo.org/show_bug.cgi?id=3150


aklapper at openismus.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |aklapper at openismus.com
           Keywords|                            |moreinfo
            Summary|segfault  in libfontconfig  |segfault in libfontconfig
                   |when using optimization     |when using -O0 in
                   |level 0 in application /    |application / nokia sans
                   |nokia sans font             |font




------- Comment #1 from aklapper at openismus.com  2008-09-26 16:35 GMT+3 -------
Is this only gpe-calendar that is compiled without optimizations or GTK and/or
libfontconfig too?


(In reply to comment #0)
> SOFTWARE VERSION:
> (Control Panel > General > About product)

Please DO enter this information.

> STEPS TO REPRODUCE THE PROBLEM:
> (have a system that can run gpe-calendar.)

What does that mean? N810 e.g.?

> Get source for gpe-calendar.

Can you provide an URL? Please make this easy for developers to reproduce...

> set DEB_BUILD_OPTIONS to noopt. build package and
> install on device.

Can you provide the exact commands you've used?

> ACTUAL OUTCOME:
> program segfaults due to null pointer

Can you provide the exact output here, please?

> OTHER COMMENTS:
> fcpat.c:FcPatternBuild returns 0 at some point when the font Nokia Sans is
> used. Does not crash when the application is compiled with "-O2" . swap is
> enabled and there should be memory free.


-- 
Configure bugmail: https://bugs.maemo.org/userprefs.cgi?tab=email
Replies to this email are NOT read, instead please add comments at
https://bugs.maemo.org/show_bug.cgi?id=3150
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

More information about the hafqa mailing list