From: Vladimir Prus <ghost@cs.msu.su>
To: gdb@sources.redhat.com
Subject: Re: step into next source line (that belongs to me)
Date: Tue, 26 Dec 2006 20:21:00 -0000 [thread overview]
Message-ID: <ems07o$9p1$1@sea.gmane.org> (raw)
In-Reply-To: <20061226151958.GA16027@nevyn.them.org>
Daniel Jacobowitz wrote:
> On Tue, Dec 26, 2006 at 01:19:00PM +0100, Christian Parpart wrote:
>> Is there a way to do such things using gdb?
>
> Not yet, no. But it could probably be added using your definition of
> interesting files.
FWIW, it is not obvious this should be in GDB. The frontend might be
in a better position to conveniently specify which files to ignore,
and all that's needed is emitting "finish + step" when
entering "non-interesting" function. I planned to implement
some "auto-finish" functionality in KDevelop for quite some time.
- Volodya
next prev parent reply other threads:[~2006-12-26 20:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-26 11:18 Christian Parpart
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 [this message]
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='ems07o$9p1$1@sea.gmane.org' \
--to=ghost@cs.msu.su \
--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