From: Daniel Jacobowitz <drow@mvista.com>
To: Iso-H <jd@ts.ray.fi>, gdb@sources.redhat.com
Subject: Re: gdb-5.x and step over inline functions
Date: Mon, 19 Aug 2002 08:48:00 -0000 [thread overview]
Message-ID: <20020819154909.GB7772@nevyn.them.org> (raw)
In-Reply-To: <20020224133415.A12371@nevyn.them.org>
On Sun, Feb 24, 2002 at 01:34:15PM -0500, Daniel Jacobowitz wrote:
> On Sun, Feb 24, 2002 at 08:09:11PM +0200, Iso-H wrote:
> > On Sun, 24 Feb 2002, Iso-H wrote:
> >
> > > On Sun, 24 Feb 2002, Daniel Jacobowitz wrote:
> > >
> > > > On Sun, Feb 24, 2002 at 03:14:00PM +0200, Iso-H wrote:
> > > > >
> > > > > On Sun, 24 Feb 2002, Eli Zaretskii wrote:
> > > > >
> > > > > >
> > > > > > On Sun, 24 Feb 2002, Iso-H wrote:
> > > > > >
> > > > > > > Is there any way to step over inline functions
> > > > > > > when using gdb >= 5.1 ? Some (commandline or other)option
> > > > > > > perhaps?
> > > > > > ....
> > > >
> > > > Could you provide a small testcase, with source and a compile
> > > > commandline?
> > >
> > > It seems to be so that it is difficult to create
> > > just simple "demo", but I'll try...
> > >
> >
> > Ok. here it is; one file only ;)
>
> > As you can see, gdb doesn't show "f_func", but Demo_t's
> > constructor instead !
>
> Thanks! I think I see what's going on; I'll take a better look at it
> later tonight.
And, eight months later...
This is unfortunately a GCC bug. The debug information says that the
beginning of the function is on line 17, in the inline constructor;
nothing GDB can do about that. I'm not quite sure if this is fixed or
avoided in GCC 3.1, but the problem doesn't show up.
If you use GCC 3.1, you'll notice that list behaves properly but break
drops you in an inline function; that's symptomatic of two things:
- GDB's lack of proper support for inline functions
- GDB's prologue skipping, as Andrew was discussing this weekend.
Both of these should be resolved but there's no clear time frame on
either.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-08-19 15:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-24 5:14 Iso-H
2002-02-24 8:40 ` Daniel Jacobowitz
2002-02-24 9:25 ` Iso-H
2002-02-24 10:09 ` Iso-H
2002-02-24 10:34 ` Daniel Jacobowitz
2002-08-19 8:48 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-02-24 12:33 Michael Elizabeth Chastain
2002-02-24 13:29 ` Iso-H
2002-02-25 23:44 ` Iso-H
2002-02-24 11:33 Michael Elizabeth Chastain
2002-02-24 11:45 ` Iso-H
2002-02-24 8:30 Salman Khilji
2002-02-24 2:37 Iso-H
2002-02-24 3:12 ` 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=20020819154909.GB7772@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=jd@ts.ray.fi \
/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