Thursday, September 18, 2008
Cadence Encounter SEGV on start faults cured III
It is the fonts. I had similar segv crashes using X on windows without the fixed and misc fonts installed. Seems Cadence likes its traditional X client setup. Now I just need to diagnose what font packages I haven't installed / installed in the wrong places.
Subscribe to:
Post Comments (Atom)
Laird Tpcm 7250 is as good as Honeywell PTM7950 as thermal paste / interface for PC
[This is not very scientific, however it is notable. At 7.5W/m-K vs the installed SYY-157 at 15.7 W/m-K it performed better in real world lo...
-
[WARNING: Some people are reporting that following the steps for them does not fix the problem. I am working on trying to find out what the ...
-
[Credit for the fix goes to Todd Wild] Just had a weird problem with my Weller WSL with WMP pencil: Symptom of initial failure: The bas...
-
Gigabyte i-RAM or GC-RAMDISK, PCI version The Gigabyte i-RAM (or GC-RAMDISK) is a curious device. I have always been uncertain if it w...
Thanks so much!
ReplyDeleteI've been trying to overcome the SEGV errors for a whole week. Installing the missing fonts on my NX-Client cured them. Strange thing is that SoC Encounter did work for a couple of times without the fonts, then started crashing.
I've exactly the same problem with Fedora 11 and SoC Encounter 8.1 32 bit.
ReplyDeletesotiris, can you tell us installing (exactly) which font package solved this?
thanks in advance