debugging problems

[John Birch]

On Tue, 30 Jan 2001 20:04, Scott Manson wrote:
> On Tuesday 30 January 2001 12:37 am, you wrote:
> > Hi,
> > I am having some strange problems when I try to debug with the
> > integrated debugger. I am trying to debug an application called
> > kgraphspace that was build w/ kdevelop and uses libtool. The integrated
> > debugger doesn't seem to be able to interact with the running  program.
> > I can't seem to set and remove breakpoints after the program has
> > started to run and I can't seem to interrupt it either. Very strange...
> > Sometimes it wont even start I need to hit run at least 3 times because
> > of some breakpoints in shared libraries.
> >
> > My version of kdevelop-1.4 from cvs with kdelibs-2.0.1 hacked to
> > compile on Solaris6 with gdb-5.0. Maybe the problem is gdb-5.0?
> >
> > Has anybody made similar experiences?
>
> I have ran into same problem sadly I don't know of a fix but if you
> configure static libraries you will be able to single step and set
> breakpoints in code if you developing then for a "release" version you can
> go ahead and make shared libraries.  IIRC others have had problems and some
> of the solutions upgrading to gdb-5 didn't fix it for me so I just make
> static libraries for debugging purposes.

hmm - not enough info here to make a reasonable stab at the problem.

Try recompiling kdevelop with the switch -DGDB_MONITOR (the easiest way to do 
this is to use kdevelop to compile kdevelop as the project has the switch 
already - copy kdevelop.kdevprj.save to kdevelop.kdevprj) This will give you 
an extra output tab (debugger) that shows the messages being passed between 
gdb and kdevelop. This should give us a good insight into where the problem 
resides.

Roland and Scott i suspect the breakpoints in shared libs problems are 
different (unless you both are using Solaris?) I'd like to know why this 
doesn't continue when a lib is loaded. BTW You can turn this option off in 
the debugger options (KDevelop Setup/Debugger/Try setting BP's on lib load) 
but please read at least the tool tip on what it is trying to do. More info 
can be found in the comments at the top of the source gdbcontroller.cpp, and 
in the manual in the section on the debugger. Scott, changing the libs to 
static libs is not the real solution. You need to either raise a bug report 
or (preferrably) contact me so we can work out a solution. If others are 
having this problem please speak up and let me know so that it can be fixed. 
I have no problems with this at all, so I need your help to find out why 
others do.

> PS: Why dont you guys backport some of your good ideas from kdevelop-2
> and keep this baby (1.4) alive? I mean, better to have a slowly
> changing but funtioning program than none at all. :-) Yeah I now, I'm
> sitting here on my smart ass making stupid remarks nobody asked for,
> but maybe the one or other has thought of this too....

Actually, I disagree I want 1.x code to finish soon and be replaced with the 
2.0 code (even though I did the port to 1.4!!). But there is only so much 
time we can spend on this. It needs others to front up and help out. What you 
are suggesting would be very difficult (read impossible) given what the 2.0 
code is trying to do and the state of the 1.x code.

jbb

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