Andreas Pakulat apaku at gmx.de
Tue Jun 17 14:08:30 UTC 2008

On 17.06.08 17:34:44, Evgeniy Ivanov wrote:
> Andreas Pakulat wrote:
> > On 16.06.08 18:51:39, Evgeniy Ivanov wrote:
> > So what did you do to make it crash? I've just tried creating a new
> > qmake project (note the other projects are from kdesdk if you have that
> > installed and might not work, though they should I think) and imported
> > that into a local svn (using file:///....).
> >
> > And of course a backtrace would help.
> >   
> mkdir svnrepo
> cd ./svnrepo/
> svnadmin create proj1
> vim ./proj1/conf/svnserve.conf
>        anon-access = read
>        anon-access = write
> kdevelop &
> QMake based project, SVN, Repo: file:///workspace/trash/svnrepo/proj1/  

Aah, yeah that one is actually "well known" :) The reason it crashes is
that the import expects you to fill in the exact directory which should
be created for the project, i.e.

Of course it shouldn't crash, but I didn't yet get around to fixing

> (without file:/// is the same). Then I can get a backtrace :( But 
> unfortunately I can't, for an hour my laptop didn't respond and then I 
> got «Failed to create backtrace» or something like it. I have to buy 2Gb 
> RAM, but can't go to the sop earlier than weekend. Do you think 2Gb is 
> enough to debug and see backtraces?

Hmm, I don't have a problem getting a backtrace and I doubt that more
memory will help you there. The kde crash dialog is pretty slow/memory
consuming anyway (for no good reason IMHO), its better to either run
kdevelop with gdb by attaching it, or by letting it create a core file.
For that I'm starting kdev4 with a little shell script like this:

ulimit -c 100000
kdevelop --no-crashhandler

this disables kde's crash dialog and thus you get a core file. Then you
can start gdb on the core file and let it print a backtrace, which
usually is a lot faster.


Living your life is a task so difficult, it has never been attempted before.

More information about the KDevelop-devel mailing list