Thanks all, I have implemented all suggestions including the idea of having a separate debug installation of gtk. gdb now shows results in the detail required including references to my files.
On Sat, 2005-05-14 at 18:15, Stefan Kost wrote: > Hi Daniel, > > what I do is to have the same version of gtk and glib I have from portage > installed again to my homedir built from source. > So I have $HOME/debug with debug version of some libs. When I have to gebug I > just lauch the app as > env LD_LIBRARY_PATH=$HOME/debug/lib gdb ./my-app --g-fatal-warnings > > Stefan > > Thanks Oliver, > > > > I tried that but it is still the same. Do I have to have gtk+/glib etc > > compiled with the debug option? (I use gentoo) > > > > > > On Sat, 2005-05-14 at 17:19, Olivier Ramare wrote: > > > >>Hi, > >>I usually compile with the additionnal flag -ggdb > >>then gdb ./Sol.o (mine is called Sol.o these days :-)) > >>and run --sync as a gdb command. Then "where" or "bt" > >>usually shows me where things go wrong : gdb puts > >>last call first, so after #2, you should get the name on > >>the function who called it (from your own code) > >>as well as the file name and the line number in this > >>file (dont edit the file in between !!) to locate > >>precisely where it went wrong. That's usually very > >>efficient (except when some pointers go awry :-() > >> > >>HTH, > >>Amities, > >> Olivier > > > > > > _______________________________________________ > > gtk-app-devel-list mailing list > > gtk-app-devel-list@gnome.org > > http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
