From: Daniel Jacobowitz <drow@false.org>
To: Edward Peschko <esp5@pge.com>
Cc: gdb@sources.redhat.com
Subject: Re: suppressing stepping into standard library functions
Date: Wed, 16 Feb 2005 12:04:00 -0000 [thread overview]
Message-ID: <20050216043404.GA16406@nevyn.them.org> (raw)
In-Reply-To: <20050216041125.GA16018@venus>
On Tue, Feb 15, 2005 at 08:11:25PM -0800, Edward Peschko wrote:
> > > when hitting 'n' in the debugging sessions really obfuscates the flow of
> > > logic of the program. I'd like to step through my code, and my code only.
> > >
> > > Is there a way to configure gdb to avoid stepping into certain
> > > classes/functions like this?
> >
> > Not yet - this requires support for inline functions, so that we can
> > recognize when we're leaving the user code.
>
> so..
>
> Is support for inline functions slated for 6.4? And if I compiled with
> -fno-inline, could I get around this?
It's slated for whenever someone does the work, so no :-)
I'm not sure if -fno-inline really suppresses all inlining. May depend
on your GCC.
--
Daniel Jacobowitz
CodeSourcery, LLC
prev parent reply other threads:[~2005-02-16 4:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-12 6:52 Edward Peschko
2005-02-12 19:45 ` Daniel Jacobowitz
2005-02-16 4:34 ` Edward Peschko
2005-02-16 12:04 ` Daniel Jacobowitz [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=20050216043404.GA16406@nevyn.them.org \
--to=drow@false.org \
--cc=esp5@pge.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