segfaults

[holle at almaden.ibm.com]

Looking at the stack-trace I think the segfault is inside Qt and not inside
KDevelop ore KDE.

What library versions of Qt and KDE are you using ? Anything like "pre" or an
outdated Qt perhaps, like 1.2 ?

- holger

Virgil King <vking at mit.edu> on 02/08/99 07:00:50

Please respond to kdevelop at fara3.cs.uni-potsdam.de

To:   kdevelop at fara3.cs.uni-potsdam.de
cc:
Subject:  Re: segfaults






Here's the gdb transcript, using kdevelop 1.0b1. Now it crashes just as the
main window finishes rendering behind the tips window. Thanks for the help.

(gdb) run
Starting program: /opt/kde/bin/kdevelop

Program received signal SIGSEGV, Segmentation fault.
0x406e359e in main_arena ()
Current language:  auto; currently c
(gdb) where
#0  0x406e359e in main_arena ()
#1  0x40643f06 in buffered_vfprintf (s=0x406e3500,
    format=0x401c58ef "Qt: gdb: -nograb added to command-line options.\n\t Use t
he -dograb option to enforce grabbing.", args=0xbffff880) at vfprintf.c:1752
#2  0x4063f856 in _IO_vfprintf (s=0x406e3500,
    format=0x401c58ef "Qt: gdb: -nograb added to command-line options.\n\t Use t
he -dograb option to enforce grabbing.", ap=0xbffff880) at vfprintf.c:1018
#3  0x401345f5 in debug ()
#4  0x40184af5 in qt_init_internal ()
#5  0x4018520d in qt_init ()
#6  0x400f3d35 in QApplication::QApplication ()
#7  0x4054fb9a in KApplication::KApplication ()
#8  0x404b35c0 in KWMModuleApplication::KWMModuleApplication ()
#9  0x8075184 in main (argc=1, argv=0xbffffcd4) at main.cpp:29
#10 0x40612cb3 in __libc_start_main (main=0x8075140 <main>, argc=1,
    argv=0xbffffcd4, init=0x805f07c <_init>, fini=0x81e95b0 <_fini>,
    rtld_fini=0x4000a350 <_dl_fini>, stack_end=0xbffffccc)
    at ../sysdeps/generic/libc-start.c:78

On Fri, 30 Jul 1999, you wrote:
>On Fri, 30 Jul 1999 Virgil King wrote:
>>Segmentation fault      (core dumped) kdevelop
>>
>>After opening a project. Can I compile kdevelop to be more verbose?
>
>./configure --enable-debug is always a good idea. Apart from
>that, you get at least information _where_ the segfault
>occured if you load it into the debugger with 'gdb kdevelop',
>then 'run' and when it crashes, type 'where'.
>
>Bernd.