kdevelop SEG FAULTS!...debug data

[Bob Bernstein]

Bob Bernstein <ruptured-duck at home.com> wrote:

> kdevelop was then built from the KDEVELOP_1_0 branch. All it wants to do is
> seg fault. This same behaviour is displayed whether I build from the
> kdevelop19990906.tar.gz snapshot, or from the kdevelop-1.0beta2.tar.gz
> tarball, and now, from the cvsup sources.

I rebuilt with debug; here's the 'where' story:

(gdb) run
Starting program: /usr/local/kde/bin/kdevelop 

Program received signal SIGSEGV, Segmentation fault.
0x40625d4c in buffered_vfprintf () from /lib/libc.so.6
(gdb) where
#0  0x40625d4c in buffered_vfprintf () from /lib/libc.so.6
#1  0x40621afc in vfprintf () from /lib/libc.so.6
#2  0x4013a21f in debug () from /usr/local/qt/lib/libqt.so.1
#3  0x401921f2 in qt_init_internal () from /usr/local/qt/lib/libqt.so.1
#4  0x401929cf in qt_init () from /usr/local/qt/lib/libqt.so.1
#5  0x400f4235 in QApplication::QApplication ()
   from /usr/local/qt/lib/libqt.so.1
#6  0x405089d9 in KApplication::KApplication ()
   from /usr/local/kde/lib/libkdecore.so.2
#7  0x40475fb3 in KWMModuleApplication::KWMModuleApplication ()
   from /usr/local/kde/lib/libkdeui.so.2
#8  0x807bee7 in main ()
#9  0x405fe282 in __libc_start_main () from /lib/libc.so.6

I don't know enough to be able to interpret this. What seems to be the
culprit?


--
Bob Bernstein                http://members.home.net/ruptured-duck

Any resemblance to real persons living or dead is purely coincidental. Void
where prohibited. Some assembly required. List each check separately by bank
number. Batteries not included. Contents may settle during shipment. Use only
as directed.