Am Dienstag, 18. September 2012 schrieb Nick Boyce: > > Similar it goes for others like: > > > > > > #19 0x00007f801b4d96f2 in g_main_context_dispatch () from > > /lib/libglib-2.0.so.0 #20 0x00007f801b4dd568 in ?? () from > > /lib/libglib-2.0.so.0 > > #21 0x00007f801b4dd71c in g_main_context_iteration () from > > /lib/libglib-2.0.so.0 > > > > > > > > But then this one does already seem installed its just that > > particular address that gdb can´t resolve. > > > > > > > > You can do this with almost all references in there. > > [snip] > > Thanks for the explanation - I think I'm beginning to get the hang of > it now, though would very much like to understand how some function > names can remain unresolvable while others in the same package > (libglib in this instance) are not. Maybe they're private functions of > some sort, or maybe the compiler can be told that some names are of no > interest. I guess I'll understand better by writing a KDE program or > two
I have no idea about this one either. Cheers, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: http://lists.debian.org/[email protected]
