Custom Query (204 matches)
Results (67 - 69 of 204)
| Ticket | Owner | Reporter | Resolution | Summary |
|---|---|---|---|---|
| #82 | fixed | fontconfig: Implement atomic primitives | ||
| Description |
Turns out that our GCC does't support built-in functions for atomic memory access, see https://github.com/psmedley/gcc/issues/19. Fontconfig provides a fallback but it's not thread-safe. We should add these functions ourselves to make sure that there are no races when several applications access fontconfig at the same time. |
|||
| #83 | wontfix | ash: crash when using BEGINLIBPATH | ||
| Description |
Given the following script BEGINLIBPATH='foo' t2.sh
and the empty script sh t.sh will result into the following crash: LIBC PANIC!! _um_free_maybe_lock: Tried to free block twice - block=00032a54 lock=0x1 pid=0x1ef1 ppid=0x1ef0 tid=0x0001 slot=0x00da pri=0x0200 mc=0x0000 ps=0x0010 C:\USR\BIN\SH.EXE Process dumping was disabled, use DUMPPROC / PROCDUMP to enable it. [1] Killed BEGINLIBPATH="fo...
It in particular hurts the install target of python when the |
|||
| #86 | fixed | After fontconfig was updated CR3 doesn't start | ||
| Description |
I am not quite sure if this is the proper placer to report this or if the following is really the cause but... After the latest update of fontconfig (yum updated fontconfig-legacy 2.11.94-1 and by yum installed fontconfig 2.11.94-1 CR3 won't start. Redirecting stdout and stderr gives: 2016/01/06 23:03:57.0000 WARN Changing log level from 3 to 1 2016/01/06 23:03:57.0000 WARN Reading list of system fonts using FONTCONFIG 2016/01/06 23:03:57.0000 WARN FONTCONFIG: 0 fonts registered Fatal Error: Cannot open font file(s) .ttf Cannot work without font Cannot init CREngine - exiting |
|||
