Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Iso-H <jd@ts.ray.fi>
To: gdb@sources.redhat.com
Subject: Re: gdb-5.x and step over inline functions
Date: Sun, 24 Feb 2002 05:14:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.21.0202241513220.16535-100000@alphatux2.ts.ray.fi> (raw)


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?
> 
> Doesn't `until' do that?  That is, given that line 123 calls an inline 
> function, and line 124 is the one after the inline function returns, you 
> should be able to say "until 124" and get what you want.  Does that work?

  It isn't same; for example if I want to say: "list f_MyFunction"
  and if there is (==beginning of "f_MyFunction") some objects 
  which have inline constructors I get list of those constructor(s)
  NOT list of "f_MyFunction" as I expected/wanted.  Besides, 
  I have to check what is the line number from source code by editor 
  because gdb can't show that line to me.

  Same goes with "next"; if I set breakpoint: "b f_MyFunction"
  I don't get what I want, because I end up to inside of those
  f*king inline constructor(s) again when breakpoint is reached!

  All this works with gdb-5.0, so gdb-5.1.x behaves
  differently here...

> 
> >  I have used gcc option "-g3" with compilations and
> >  my host/target arch is GNULinux-alpha (ev56/ev67) but
> >  I think that this "step over inline functions" problem
> >  exist on other archs too.
> 
> Does it help to use -gstabs+ instead of -g3?  (I assume the latter is a
> synonym for -gdwarf-2 on your system.)

  I tried, but it didn't help...

> 

-- 

Iso-H



             reply	other threads:[~2002-02-24 13:14 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-24  5:14 Iso-H [this message]
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
  -- 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=Pine.LNX.4.21.0202241513220.16535-100000@alphatux2.ts.ray.fi \
    --to=jd@ts.ray.fi \
    --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