Bug 89767 - "Setting->Configure Kile" crashes Kile
Summary: "Setting->Configure Kile" crashes Kile
Status: RESOLVED FIXED
Alias: None
Product: kile
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: Jeroen Wijnhout
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-09-18 15:05 UTC by shayne.flint
Modified: 2004-10-05 16:51 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description shayne.flint 2004-09-18 15:05:21 UTC
Version:           1.7b2 (using KDE KDE 3.3.0)
Installed from:    Gentoo Packages
OS:                Linux

Kile crashes when I select "Settings->Configure Kile" from the menu bar.

If I start Kile from a shell, I get the following error message when Kile crashes:

QWidget::setMaximumSize: (m_stackExtra/QWidgetStack) Negative sizes (32767,-1) are not possible
Alarm clock
Comment 1 Jason LeBrun 2004-09-21 02:02:20 UTC
I have the same problem. Here's a backtrace from the CVS version:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1102598864 (LWP 23356)]
0x419fc1ea in std::__default_alloc_template<true, 0>::allocate ()
   from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.so.5
(gdb) bt
#0  0x419fc1ea in std::__default_alloc_template<true, 0>::allocate ()
   from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.so.5
#1  0x419fc270 in std::allocator<char>::allocate () from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.so.5
#2  0x41a031c5 in std::string::_Rep::_S_create () from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.so.5
#3  0x419ff30f in std::string::_M_mutate () from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.so.5
#4  0x41a03e80 in std::string::_M_replace_safe<char const*> ()
   from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.so.5
#5  0x41a00ce4 in std::string::assign () from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.so.5
#6  0x41fc1e4a in ?? ()
#7  0xbfffcc94 in ?? ()
#8  0x420052f4 in ?? ()
#9  0x00000000 in ?? ()
#10 0x41a36ce4 in std::__default_alloc_template<true, 0>::_S_free_list ()
   from /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.4/libstdc++.so.5
Comment 2 Jeroen Wijnhout 2004-09-22 11:56:45 UTC
This backtrace doesn't tell me much. I fixed the problem mentioned by the OP, perhaps this fixes the crash. Can you update your source code (after say 22/09/2004 15:00 CET)?

best,
Jeroen
Comment 3 shayne.flint 2004-09-23 14:24:33 UTC
I just built kile from CVS - hasn't fixed the problem - still crashes on selecting "Settings->Configure Kile"
Comment 4 Jeroen Wijnhout 2004-09-23 14:26:45 UTC
Ok, thanks anyway. Did you compile with
./configure --enable-debug=full
the backtrace will be more useful.

best,
Jeroen
Comment 5 shayne.flint 2004-09-24 02:36:05 UTC
After rebuilding with ./configure --enable-debug=full I get this bt from gdb.

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 29927)]
0x40d3cea0 in posix_memalign () from /usr/kde/3.3/lib/libkdecore.so.4
(gdb) bt
#0  0x40d3cea0 in posix_memalign () from /usr/kde/3.3/lib/libkdecore.so.4
#1  0x41a7a130 in __fpu_control () from /lib/libc.so.6
#2  0x419ce003 in _IO_un_link () from /lib/libc.so.6
Previous frame inner to this frame (corrupt stack?)
(gdb)                                                 
Comment 6 P. Hoffmeister 2004-10-01 17:43:18 UTC
I got exactly the same problem.
Comment 7 Jeroen Wijnhout 2004-10-01 18:03:23 UTC
On Friday 01 October 2004 17:43, P.Hoffmeister wrote:
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>
> http://bugs.kde.org/show_bug.cgi?id=89767
>
>
>
>
> ------- Additional Comments From hoffmeis gmx net  2004-10-01 17:43 -------
> I got exactly the same problem.

Please report what kind of system you are using (distro, Qt and KDE version).

best,
Jeroen

Comment 8 P. Hoffmeister 2004-10-03 10:09:33 UTC
Sorry, I meant the same problem on the sme system, so its:
Gentoo, KDE 3.3.0, QT 3.3.3, Kile 1.7b2.
Comment 9 shayne.flint 2004-10-03 12:45:29 UTC
Just to confirm my config:

Gentoo, KDE 3.3.0, QT 3.3.3-r1, Kile 1.7b2. 
Comment 10 Jeroen Wijnhout 2004-10-04 09:54:26 UTC
Do you know who the Gentoo packager is? I can't confirm this bug with KDE 3.3.1 and Qt 3.3.2, or KDE 3.2.0 with Qt 3.3. The backtrace shows the crash occurs in very low-level libraries, pointing to (perhaps) a packaging problem (conflicting GNU C-library for example).

best,
Jeroen
Comment 11 P. Hoffmeister 2004-10-04 10:24:08 UTC
I think the maintainer is "carlo at gentoo dot org"
Comment 12 shayne.flint 2004-10-04 15:56:44 UTC
Well, I just did an update of my gentoo distribution (emerge -up world). It updated a bunch of stuff that seemed unrelated, but it fixed the problem.

kile 1.7b2 now works OK.
Comment 13 P. Hoffmeister 2004-10-04 18:24:22 UTC
I can confirm that. After updating man, rsync, pygtk and aspell. The bug vanished.  
I then downgraded to the old versions of these programs, but there was still no problem.
Comment 14 Jeroen Wijnhout 2004-10-05 16:51:00 UTC
According to the packager the bug should first be reported at bugs.gentoo.org, you can put your comments here:
http://bugs.gentoo.org/show_bug.cgi?id=66109

The problem looks like a local issue, especially since after upgrading and downgrading again the issue was solved.

I consider this issue solved until I hear otherwise.

thanks for using bugs.kde.org,
Jeroen