From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kevin Buettner To: Peter Jay Salzman , gdb mailing list Subject: Re: a question about (new behavior with?) gdb Date: Tue, 14 Aug 2001 16:08:00 -0000 Message-id: <1010814230803.ZM30488@ocotillo.lan> References: <20010814114958.A14214@dirac.org> X-SW-Source: 2001-08/msg00133.html On Aug 14, 11:49am, Peter Jay Salzman wrote: > does gdb now know about which functions belong to the C library and ignore > them for stepping purposes? No. > or is gdb ignoring functions for which it > doesn't have debugging into? ^^^^ info Yes. > one last question. i've noticed a new function on the call stack: > > (gdb) backtrace > #0 main () at try1.c:5 > #1 0x4003e46b in __libc_start_main () from /lib/libc.so.6 > > i don't remember seeing __libc_start_main() before. is that a wrapper > function for gdb? is that what's hiding frames that belong to glibc? __libc_start_main() is the glibc function responsible for calling main(). It is not the reason that you are no longer able to step into the functions in glibc. Simply recompiling glibc so that it has debugging info (line number information and the like) will enable you to step into these functions again. Kevin