Compiled using Gcc 2.95.3, use flags "-march=i686 -O3 -fexpensive-optimizations -frerun-loop-opt -fomit-frame-pointer -frerun-cse-after-loop" I can run certain Qt and KDE apps with no consequence, kuser, qtella, kopete and little apps like that work fine. But it seems as though base KDE programs like Kmenu, konq and kmail certainly like locking my system up. I have been in icewm for the past 6 or 7 days because of this. I have recompiled kde a few times with no change in stability. I have erased my .kde dir and checked the logs. It doesn't seem like anything conspicuous stuff is going on, all I know is that I can't use KDE and am really pissed about it.
You're almost certainly overoptimizing your system. Excessive optimization can reduce perfectly correct code to broken status. I'd suggest you limit yourself to -O3 -march=whatever -fomit-frame-pointer; anything else is risky and besides almost certainly won't bring about a really noticeable increase in speed. If you really need extra speed, try building a gcc3-based system (the 1.3 release series); for some processors (fex. athlons) it creates much faster code than gcc2 does. Recompile KDE with more conservative flags, better yet your whole system. You may lose a percent or two in speed but you'll gain a lot in stability, even in the event that what you're expiriencing isn't being caused by overoptimization (which is IMO unlikely).
I just recompiled KDE with pratically no flags whatsoever and it appears that that isn't the case....sadly. I wish there was some obvios solution, but I have tried everything in my power to resolve this problem and still nothing.
Um this is a fairly critical bug. No one can help?
After much crashing I have realized that the thing crashing my system is not kde per se..... It is definitly konqueror and possibly kmail. This is quite an annoying bug and I can't believe that no one else out there is experiencing the same thing. I will use opera and slypeed....but I shouldn't need to.
I'm sorry that I can't suggest anything but there are no symptoms to go on. The idea of overoptimization may still hold if you've overoptimized something other than kde, a library or something. But that's farfetched. Run konqueror/kmail from a termianl if you haven't tried it yet, maybe there's some useful message before it locks up? A userspace app shouldn't be able to hard-lock the entire system, maybe change your kernel or kernel conf or something? Compile kde with debugging (export DEBUG=1 and e.g. CXXFLAG,CFLAGS=-O0 -g3), get a traceback of the crash (again running from a cosole) and submit to bugs.kde.org?
What's your status? Any good news? Maybe you should try kde cvs?
Oh yeah, the status is that I am a freaking idiot. :) I did somthing I should've tried a LONG time ago and it fixed the problem. I erased my /etc/X11/XFree86Config file and rewrote if from scratch adding one module/option at a time. Turns out my config was telling certain things to take over certain duties (apggart as oppest to nvagp) and that screwed somthings up. Now I really have no idea why this effected only kmail and konq, but I assume that khtml or fast writeing or somthing like that was the perp. Anywho I'm an idiot. Have a nice day.
Well - shit happens. At least it's solved now. Have a nice day :-)
