Kdevelop-3.0.1 KDE-3.2.0 QT-3.3.0-r1 Python-2.3.3 GCC-3.3.2-r5 Hardened-gcc-3.3.2.1-r2 Reproducible: Always Steps to Reproduce: 1. Emerge kdevelop with hardened-gcc and -fstack-protector in your cflags 2. Open a file or project in kdevelop 3. Close a file, or quit kdevelop Actual Results: Kdevelop crashes Expected Results: Not crash, but quitetly close the file or quit kdevelop. To fix the problem, remerge kdevelop without hardened-gcc and -fstack-protector.
resolve bug, changing resolution to FIXED
Re: "To fix the problem, remerge kdevelop without hardened-gcc and -fstack-protector." How would that fix? The overflow still exists correct?
it is a "temporaly" fix, yes. Sorry for not being clear on that. reopening bug.
solution 1) unmerge hardened-gcc and only use -fstack-protector in /etc/make.conf:CFLAGS, then recompile the KDE and the kdevelop application solution 2) if you are feeling brave and can probably trash your machine, test gcc-3.3.3-r1 with USE="hardened", then recompile KDE and kdevelop it should be noted that a full world compiled with fstack-protector is usually more "sane" than some applications only. Do you happen to have parts or all of the KDE libraries and executables compiled with stack protector from before November/December 2003 where we moved the propolice to glibc? If yes, recompiling those parts of the system should also solve the problem with the dying kdevelop.
"Do you happen to have parts or all of the KDE libraries and executables compiled with stack protector from before November/December 2003 where we moved the propolice to glibc?" No, I recompiled world with hardened-gcc and -fstack-protector earlier this year. I think I'll try gcc-3.3.3-r1, and reply with the result.
Ok, finally ive recompiled kdevelop. I had to use solution 1, as gcc.3.3.3-r1 won't compile. (As it's still -*, I'll leave it and try again when it's updated.)
Recompilation with USE="hardened" gcc-3.3.3-r1 don't solve the problem. kde 3.2.1 qt 3.3.1-r1 BTW kdevelop 3.0.2 have same bug, it crashes while file closing.
Problem is with KDE and QT and the likes. Reopen a bug with the gentoo kde developers/maintainers if problem persists.
