On Thursday, November 21, 2002, at 10:02 AM, Martin Costabel wrote:
Well I suspected this so I set "limit stacksize unlimited" in the terminal window before running a compilation of koffice a week or so ago. It still gave a segmentation fault and in the same place. I can try it with this one. Why would kde builds be the only things to hit a hardware problem? Shouldn't there be other visible problems with the machine?On jeudi, nov 21, 2002, at 13:32 Europe/Paris, Benjamin Reed wrote:One thought: Has one of the people having these crashes tried to set the stacksize to a higher value, "limit stack 2000" or something like that? I remember some stacksize related crashes that looked like this. OTOH, the places where these crashes here happened didn't look like very stack-intensive. Well, just something to check...
I'm not sure where to point you for help debugging, it sounds like you may have a hardware issue. Those kinds of crashes shouldn't be happening...
I only get these errors with builds of kde things (kdelibs3-ssl and koffice). Ton loads of other fink-driven compilations run without problem.
In the notes for the openoffice mention that there are problems that can be cured by switching the machine from dual to single processor mode. I've thought of trying that too, but fear has held me back...
-Ross-
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Fink-beginners mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-beginners
