Version: 1.9 (using KDE KDE 3.5.1) Installed from: Slackware Packages Compiler: gcc 3.4.5 OS: Linux Compiled with two methods, ./configure with processor specififc CXX flags and without that. Running from console ends with seg.fault. See attachement for strace result.
Created attachment 15285 [details] Strace
Do you get a backtrace? If so, please paste it here. Does the same crash happen if you run kile as a newly-created user?
No, the crash windows doesn't appear at all. I've ran kile now using a clean profile - the same result. I'm sorry that I can't invent any other info now :(
Hi, what Slackware are you running ? I'm currently downloading 10.2 to reproduce your problem. Thanks Thomas Braun
It's Slackware almost-current. Without newest glibc, kernel and gcc.
Okay, I just got slackware installed (really nasty installation ...) and kile doesn't crash here. Are you using officical 3.5.x kde packages? Where do I get them and how to install them ? Thanks Thomas
Yes, I'm using official slackware packages (however compiled by myself, but everything works fine, as always). I'm using slackware-curretn (except newest kernel (2.4.32) and newest gcc (3.4.6) and glibc (2.3.6) in this tree). You can get those packages here: http://www.slackware.com/getslack/list.php?country=Germany See slackware-current tree.You will have to download whole ./slackware/x amd /kde directory and just do: upgradepkg *.tgz in those directorires while using Slack.
Okay, I installed all packages in kde and x but now kde doesn't start anymore because of missing libstdc++.so.6. I then installed all packacges with gcc-*3.4.6*, and after a kile recompilation it works like a charm. So the gcc 3.4.6 packages are missing in your setup. (Although I don't know if it is safe to install them ...) Regards, Thomas
Ok, I supposed that the problem may lie in glibc or gcc, But it's still amazing why only kile behaves like that with my configuration ;). Let's say that's my fault. I'm using unstable version of Slack :) Thx for help.