Getting debugging info from glibmm and gtkmm sources

José Alburquerque wrote:
> José Alburquerque wrote:
>> Hello everyone. This is my first post to this list and I just want
>> to ask a question I think someone here will be able to answer: I'm
>> contributing to wrapping gstreamer for C++ and I find that I may need
>> to debug the library. The library is wrapped using a tool called
>> glibmmproc which has also been used to produce glibmm and gtkmm. I
>> noticed that there are debugging libraries for both glibmm and gtkmm
>> (libglibmm-2.4-dbg and gtkmm-2.4-dbg). Would someone here be able to
>> tell me how these packages are generated from the sources (or give me
>> some idea)? I think I may be able to use the same method to generate
>> debugging info for gstreamermm. I'd appreciate any help. If no one
>> knows, that's fine. Thanks.
>>
>> -Jose
>>
>>
> I'm sorry; I was using checknstall which automatically strips
> libraries and executables before creating and installing a package out
> of a "make install" command so the debugging info was being removed.
> This is why I couldn't debug the library. I found how to disable the
> stripping and I can now debug the gstreamermm library. Sorry.
>
> -Jose
>
>
But if I can, may I ask another question: If I install a debugging
package (libglibmm-2.4-dbg for example), can I step into the library's
source with gdb? For example if I have the following simple code:

#include <glibmm.h>

int main (int argc, char* argv[]) {
Glib::init();
}

will gdb step into the library's code (Glib::init)? I know this seems
c++ specific, but I think it would work the same with c libraries like
glib/gtk, etc. Does anyone have some knowledge as to how to look at the
libraries source code? I know that debugging packages install the
unstripped libraries in "/usr/lib/debug/", but even if I try to use "set
debug-file-directory /usr/lib/debug" in gdb stepping into the source
still doesn't seem possible. I'd really appreciate any help. Thanks.

Sincerely
Jose


--
To UNSUBSCRIBE, email to debian-gtk-gnome-REQUEST.TakeThisOut@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster.TakeThisOut@lists.debian.org

José Alburquerque wrote:
> But if I can, may I ask another question: If I install a debugging
> package (libglibmm-2.4-dbg for example), can I step into the library's
> source with gdb? For example if I have the following simple code:
>
> #include <glibmm.h>
>
> int main (int argc, char* argv[]) {
> Glib::init();
> }
>
> will gdb step into the library's code (Glib::init)? I know this seems
> c++ specific, but I think it would work the same with c libraries like
> glib/gtk, etc. Does anyone have some knowledge as to how to look at
> the libraries source code? I know that debugging packages install the
> unstripped libraries in "/usr/lib/debug/", but even if I try to use
> "set debug-file-directory /usr/lib/debug" in gdb stepping into the
> source still doesn't seem possible. I'd really appreciate any help.
> Thanks.
>
> Sincerely
> Jose
>
>

I just needed to install the source of the packages. Thanks.

-Jose


--
To UNSUBSCRIBE, email to debian-gtk-gnome-REQUEST RemoveThis @lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster RemoveThis @lists.debian.org