kdevelop crash while debugging

[John Birch]

On Fri, 23 Feb 2001 09:27, Roland Krause wrote:
> --- John Birch <jbb at kdevelop.org> wrote:
> > What _do_ you see? I have no problems here at all. It really helps if
> > you are
> > more informative with what is happening.
>
> THere is no value for the string next to the name.
> Here is what I do:
>
> Set a breakpoint in GrepDialog::slotSearch (line 294 in the file)
> Run kdevelop in kdevelops internal debugger, go someplace and right
> click to grep something.
> Breakpoint is reached, then step through GrepDialog::slotSearch until
> files and files_temp should be initialized and have values.
>
> Now according to what you say there should be a value next to the name
> in the debugger tab but there isnt.

Not in the debugger tab but in the watch window. The debugger tab is just a 
debugging window 

(snip)

> > What system are you running on? Self compiled? rpm?
>
> Sun Solaris6, gcc-2.95.2, gdb-5.0, kde-2.1beta2, kdevelop-1.4cvs from
> the day before yesterday.
> Everything self compiled.

Ok - Solaris hmm - well you could well be the first to seriously try it and 
speak up about the problems. This could be interesting :-)

>
> > > Also kdevelop crashes when using the debugger after some time.
> >
> > Why does it crash? Could you be running out of memory?
>
> No, I have about 500 Megs and about infinite swap space, i.e.i dont
> even now.

Woohoo :-)

>
> > gdb debugging kde2
> > apps uses lots of memory, especially if the kde2 libs have debugging
> > symbols.
>
> they dont.

Good, the debugger runs way faster like this as well.

>
> > > Kdevelop is not exactly bootstrapping itself, is it?
> >
> > Works really well for me.
>
> I must be doing something really wrong, maybe its gdb-5.0.
> Appreciate your help though.

5.0 is good. You may have run into a genuine bug in kdevelop...

Want to try irc.kde.org#kde?

jbb

-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«