On Sat, Dec 3, 2011 at 08:12, Gregory Hosler <ghos...@redhat.com> wrote: > If this is your first time, perhaps don't install the debuginfo for libraries > where you think the problem isn't, and where you think you will not need to > trace into said library(s). If, during debugging, you feel that "gee, it would > be useful to set a breakpoint into that library, and see what's going on", > then > install the debuginfo for that library, and restart the debugger and your > application.
FWIW, stepping into libraries is not the only need. You might just want the symbols for those libraries for more information at debug time. To illustrate with an example: libfoo.so might provide a class dummy and you maybe using it like dummy myinstance; //. Then having the libfoo-debuginfo package installed gives you the ability to do things like, print myinstance.getattrib1() or maybe even conditional breakpoints using these symbols. -- Suvayu Open source is the future. It sets us free. -- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
