From: Erik Norvelle <lists@no...> - 2005-05-25 14:42:37
I am new to Akregator development, and relatively new to KDE. I have
done a bit of work on other KDE applications, but nothing extensive. I
am trying to set up my KDevelop environment to be able to develop
comfortably in Akregator. So far I have gotten the sources downloaded
and compiled (now using unsermake), and have built a KDevelop project
that seems to be able to properly browse and build Akregator.
My difficult is in debugging. For instance, after adding a widget to
one of the Settings panels (as a self-tutoring exercise), I am getting
a crash when I try to open "Akregator Settings" from within the
program. I'd like to be able to debug this occurrence to find out why
this is happening. However, I have been unable to get things to work.
My approach has been to run "unsermake install" before debugging. My
KDevelop "Run" configuration has "Start program in directory" set as
the Akregator source folder (so that gdb can find the sources) and the
program to be run as /home/norvelle/sw/bin/akregator, which is where I
installed the program to. My KDevelop "Debug" settings are generic...
I point KDevelop to my gdb at /usr/bin/gdb, and that's it. When I
click "Debug" in KDevelop, the gdb console window open, and it proceeds
to load the library symbols (I compiled akregator with -ggdb to add the
appropriate debug symbols). GDB then proceeds to die on a "shared
Is there anybody else who uses KDevelop to debug Akregator? I could go
back to the old-fashioned way of putting lots of logging messages into
my code, then reading logfiles to figure out what happened. But isn't
that what we have GUIs to avoid having to do?
My development environment is as follows:
Mac OS X 10.3.9