> On Fri, Jun 17, 2016 at 8:04 PM, Max Leske <[email protected]> wrote: > > Hi Petr, > > > > That looks like a bug with FreeType with our FFI. It should actually have > > been fixed but I don’t know if the VM for FreeBSD is up to date. Can you > > post the output of “Smalltalk vm version”? > > > > Cheers, > > Max > > > > Petr, Based on Max's suggestion, have you tried turning FreeType off? > World > System > Settings > Apperance > Use Free Type. > IIUC this will fall back to using built-in Strike Fonts [1], and maybe > just bypass the issue??
With FreeType off - still segfaulting. I will move this topic (+ how to debug this segfaults) to the vm mailinglist. Thanks! > > [1] > http://pharo.gemtalksystems.com/book/LanguageAndLibraries/fonts_in_pharo/strike_fonts/ > > P.S. Just curious, in the philosophy of trimming down the Pharo Image > size, are Strike Fonts a candidate for removal. It seems like having > an in-Image fall back is potentially useful when porting to new > platforms. > > cheers -ben > > > >> On 17 Jun 2016, at 13:26, Petr Fischer <[email protected]> wrote: > >> > >> Hello, I got some random segfaults (while loading Seaside) with 32 bit > >> spur vm on FreeBSD - can someone (with low level knowledge) decode > >> attached log? > >> Is this some problem with stack size? Can I fix this? > >> > >> Log: > >> http://pastebin.com/raw/NpFUnjh0 > >> > >> There is "**StackOverflow**" lines n the log... > >> > >> Thanks! pf > >> > > > > >
