From: Kevin Buettner <kevinb@cygnus.com>
To: Peter Jay Salzman <p@dirac.org>,
gdb mailing list <gdb@sourceware.cygnus.com>
Subject: Re: a question about (new behavior with?) gdb
Date: Tue, 14 Aug 2001 16:08:00 -0000 [thread overview]
Message-ID: <1010814230803.ZM30488@ocotillo.lan> (raw)
In-Reply-To: <20010814114958.A14214@dirac.org>
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
prev parent reply other threads:[~2001-08-14 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-14 11:50 Peter Jay Salzman
2001-08-14 16:08 ` Kevin Buettner [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1010814230803.ZM30488@ocotillo.lan \
--to=kevinb@cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=p@dirac.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox