Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Kris Warkentin" <kewarken@qnx.com>
To: "Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: Stepping over shared library call
Date: Mon, 11 Aug 2003 15:15:00 -0000	[thread overview]
Message-ID: <078701c3601b$5775b060$0202040a@catdog> (raw)

When I do a 'step' on a function that is in a shared library (such as
printf), what mechanisms/criteria does gdb use to determine whether to
single step all the way through it or just to stop on the next line of code?

I've observed that if the symbols are loaded for libc, gdb steps all the way
through the call but otherwise skips over it.  Is this expected behaviour?

I believe it is because one could have a situation where there is some debug
info in a shared lib (or a non-debug shared lib calls into a debug one).  If
this were the case, you'd want gdb to step until it finds some debug
information right?

Basically I'm planning on telling customers, "Use 'next' if you want to go
to the next line and only use step if you want to step into the call."  This
wouldn't be an issue if everyone just did local debugging but when you're
debugging a remote system, single stepping through a shared library call can
take a hellishly long time.

cheers,

Kris



                 reply	other threads:[~2003-08-11 15:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='078701c3601b$5775b060$0202040a@catdog' \
    --to=kewarken@qnx.com \
    --cc=gdb@sources.redhat.com \
    /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