Summary: | GNUStep: segfaults in Gorm/GWorkspace, and other apps | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | SciYro <ditopil> |
Component: | Current packages | Assignee: | Gentoo Gnustep project <gnustep> |
Status: | RESOLVED FIXED | ||
Severity: | blocker | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
SciYro
2005-07-11 15:44:11 UTC
I believe that I've seen this problem before. Could you rebuild gnustep-base with USE="ffcall -gcc-libffi", and try the applications again? If you weren't using libffi (and thus using ffcall) already, please say so. Feedback would be greatly appreciated. Also, could you post the contents of `cat /proc/cpuinfo` out of curiousity. Thanks. -- CPU Info -- processor : 0 vendor_id : AuthenticAMD cpu family : 6 model : 10 model name : AMD Athlon(tm) XP 2600+ stepping : 0 cpu MHz : 1916.714 cache size : 512 KB fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 1 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 mmx fxsr sse pni syscall mmxext 3dnowext 3dnow bogomips : 3809.28 -- -- nope, i used the ffcall thing, but it still segfaults just like usual Ahh...I may not have seen this before, actually. To clarify, did you switch to ffcall or did you use it to begin with? If you had used it to begin with, can you try it with libffi? If you USE="-ffcall -gcc-libffi" emerge gnustep-base ... it should emerge dev-libs/libffi (if you your gcc provides this, i.e. you built 3.3.5* series with gcj, you can in fact use gcc-libffi use flag). Please let me know which you started with (I had assumed you had started with libffi), and also if libffi ends up working for you. i started with the defailt (libffi), i tryed ffcall, gcc-libffi, and libffi, with no diffrence. Okay, I've seeing if anyone upstream knows anything about this (as it still seems similar an error I personally had); I have one last round of suggestions. Summary: make sure we emerge gnustep with ffcall and not libffi; run latest soon-to-be-stablized versions of gnustep core packages (which have fixes that fixed the similar issue I was having). Steps: - # emerge -pv unmerge `qpkg -I gnustep -nc` dev-libs/libffi dev-libs/ffcall --+ above assumes you have qpkg from "gentoolkit" installed --+ there aren't mant other packages that depends on the external version of libffi -- if you are running them, you'd know (e.g. sablevm); in that case, don't unmerge libffi - # ACCEPT_KEYWORDS="~x86" USE="ffcall -gcc-libffi" emerge -pv gnustep-env --+ ffcall should be merged --+ libffi should not be merged --+ Important packages that are currently ~x86: ffcall-1.10 and gnustep-base-1.10.3-r1 - merge the programs that were failing for you - let me know :-) You likely didn't merge -r1 of gnustep-base, which actually enables use of ffcall via the use flag -- I believe this may be it, if it is the problem i've seen before. Thanks for the help! thanks!, apparently ffcall was never emerged, even tho i had it set in use flags, but those commanands you gave made it install, along with everything else in gnustep, so im not seeing any more segfaults, and gorm is working fine. thanks again, now i can start using gorm/projectcenter No, thank you for testing. :-) I'm going to stabilze gnustep-base-1.10.3-r1 soon, so any updates you do should be transparent. Note that if you emerge sync before I do this, it may want to downgrade gnustep-base, so don't let it. :-) Also, for further reference, generaly, let devs close the bugs, as most keep their open bugs as a sort of TODO list. Thanks again. |