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

List:       kde-devel
Subject:    Re: kcmdisplay dumping core (KDE 2)
From:       Stephan Kulow <coolo () alpha ! tat ! physik ! uni-tuebingen ! de>
Date:       1999-04-26 19:20:10
[Download RAW message or body]

Sean Kendall Schneyer wrote:
> 
> I've started using the KDE 2 cvs code and am getting a core
> dump from kcmdisplay. Using gdb here is the stack dump
> that I get:
> 
> #0  0x408a216d in getenv (name=0x0) at ../sysdeps/generic/getenv.c:33
> ../sysdeps/generic/getenv.c:33: No such file or directory.
> (gdb) where
> #0  0x408a216d in getenv (name=0x0) at ../sysdeps/generic/getenv.c:33
> #1  0x401bf75e in KConfigBase::readEntry ()
> #2  0x806bb1a in KScreenSaver::getSaverNames ()
> #3  0x8068721 in KScreenSaver::KScreenSaver ()
> #4  0x80765d3 in KDisplayApplication::KDisplayApplication ()
> #5  0x80772b3 in main ()
> (gdb)
> 
> I'm running RedHat 5.2 (i386)
> Linux 2.2.5
> cvs source is from today
> 
> Is anyone else experiencing any problems with this? Btw, is it
> too early in the development to start sending in these types
> of reports?
> 
Ah - one more thing - use --enable-debug in kdelibs.

Greetings, Stephan

-- 
Und sie nannten ihn, wie er selbst unterschrieb -
Den Trojanischen Pferdedieb

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