Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Christian Parpart <trapni@gentoo.org>
To: gdb@sources.redhat.com
Subject: step into next source line (that belongs to me)
Date: Tue, 26 Dec 2006 11:18:00 -0000	[thread overview]
Message-ID: <200612261319.02937.trapni@gentoo.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 868 bytes --]

Hi all,

When you need to trace a c++ constructor with multiple inheritages, you maybe 
want to 'step in' to a few of them, but not all.
What I am missing is a "step in"-alike that does only step to the very next 
line that is owned by my very own source code. Everything else is not of my 
interest and just blowes you up your mind when debugging and trying to 
understand.

The code to be "my very own" could be defined as all source files under a 
specified root directory. every debugging step that can be assigned to a file 
inside this (or one of these) root directories should be used as a step. 
every other lines (e.g. caused via big header files with lots of 
inlines/templates/etc.) should be stepped over and though ignored unless 
explicitely stated.

Is there a way to do such things using gdb?

Thanks in advance,
Christian Parpart.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

             reply	other threads:[~2006-12-26 11:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-26 11:18 Christian Parpart [this message]
2006-12-26 15:20 ` Daniel Jacobowitz
2006-12-26 18:05   ` Christian Parpart
2006-12-26 18:24     ` Robert Dewar
2006-12-26 18:35   ` Jim Blandy
2006-12-26 20:21   ` Vladimir Prus
2006-12-26 20:22     ` Bob Rossi
2006-12-26 20:27       ` Vladimir Prus
2006-12-26 22:35     ` Daniel Jacobowitz
2006-12-27  8:18       ` Eli Zaretskii

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=200612261319.02937.trapni@gentoo.org \
    --to=trapni@gentoo.org \
    --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