[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: kdevelop@bero [was: Re: KDE 2.2 RELEASE]
From:       Bernhard Rosenkraenzer <bero () redhat ! de>
Date:       2001-07-30 8:29:23
[Download RAW message or body]

On Mon, 30 Jul 2001, F@lk Brettschneider wrote:

> > Bug #29808.
> > Bug #29983 may well be a duplicate.
> Unfortunately, the bugreports aint useful for reproducing the crash.

I know - haven't had the time to debug it any further than tracing it down
to CKDevelop::show().

> Furthermore I don't know people having probs with KDevelop's startup. As
> far as I know from several people it works at least on all SuSE systems
> between 7.1 and 7.2 as well as on Solaris and FreeBSD.

Doesn't work on RH 7.1 and 7.2-beta. 29983 (if it is a duplicate) seems to
be something completely different (we never shipped that compiler).

> Please, try the latest snapshot and call the setup wizard by using
> K-->Development-->KDevelop2.0Setup to reset your config files. Maybe
> your local kdeveloprc was screwed up by one of the CVS development
> versions.

That was my first thought too - tried it before writing the bug report.

(no debugging symbols found)...0x410d9c69 in __wait4 ()
   from /lib/i686/libc.so.6
#0  0x410d9c69 in __wait4 () from /lib/i686/libc.so.6
#1  0x41154484 in __DTOR_END__ () from /lib/i686/libc.so.6
#2  0x41a84178 in KCrash::defaultCrashHandler () from
/usr/lib/libkdecore.so.3

#3  <signal handler called>

(I'm currently recompiling with debugging enabled ;) )

LLaP
bero

[prev in list] [next in list] [prev in thread] [next in thread]