Mirror of the gdb mailing list
 help / color / mirror / Atom feed
* Re: gdb-5.x and step over inline functions
@ 2002-02-24  5:14 Iso-H
  2002-02-24  8:40 ` Daniel Jacobowitz
  0 siblings, 1 reply; 14+ messages in thread
From: Iso-H @ 2002-02-24  5:14 UTC (permalink / raw)
  To: gdb


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



^ permalink raw reply	[flat|nested] 14+ messages in thread
* Re: gdb-5.x and step over inline functions
@ 2002-02-24 12:33 Michael Elizabeth Chastain
  2002-02-24 13:29 ` Iso-H
  0 siblings, 1 reply; 14+ messages in thread
From: Michael Elizabeth Chastain @ 2002-02-24 12:33 UTC (permalink / raw)
  To: gdb, jd

I was unclear, I am sorry.

You wrote:
> gdb-5.0 works as expected, but now I have problem
> with gcc >= 3.x because gdb-5.0 won't work with binaries
>  compiled by gcc-3.x; when I start gdb, it only says:
> 
>     ...Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader.

I was responding to that part.

I am suggesting that you try gdb 5.0, gcc 3.x, and "-gstabs+" when you
compile.  Then you can have the "step over inline functions" behavior
that you want in gdb 5.0, while avoiding any problems with the dwarf
symbol reader in gdb 5.0.

Michael C


^ permalink raw reply	[flat|nested] 14+ messages in thread
* Re: gdb-5.x and step over inline functions
@ 2002-02-24 11:33 Michael Elizabeth Chastain
  2002-02-24 11:45 ` Iso-H
  0 siblings, 1 reply; 14+ messages in thread
From: Michael Elizabeth Chastain @ 2002-02-24 11:33 UTC (permalink / raw)
  To: gdb, jd

You could try a different debug option ("gcc -gstabs+ ...").  I don't
know if that will work on your platform but it will avoid the dwarf 2
reader issue with gdb 5.0.

Michael C


^ permalink raw reply	[flat|nested] 14+ messages in thread
* Re: gdb-5.x and step over inline functions
@ 2002-02-24  8:30 Salman Khilji
  0 siblings, 0 replies; 14+ messages in thread
From: Salman Khilji @ 2002-02-24  8:30 UTC (permalink / raw)
  To: gdb

I totally agree.  I downloaded the ACE application framework 
(www.cs.wustl.edu/~schmidt.  Download and compile 
%ACE_ROOT%/examples/C++Npv1.  There are plenty of inline functions there.  
My experience was the gdb was pretty much a useless tool for stepping thru 
the example code.  It was jumping back and forth to places of code that I 
didn't care about.    If you want to see for yourself step thru the ::open 
function included in the Logging_Server class.

I also would like to see this "stepping into inlines" an optional feature 
turned off by default.

The ACE framework uses a macro named ACE_INLINE for inline functions.  I 
dont' know what exactly this macro does.

Salman

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


_________________________________________________________________
Send and receive Hotmail on your mobile device: http://mobile.msn.com


^ permalink raw reply	[flat|nested] 14+ messages in thread
* gdb-5.x and step over inline functions
@ 2002-02-24  2:37 Iso-H
  2002-02-24  3:12 ` Eli Zaretskii
  0 siblings, 1 reply; 14+ messages in thread
From: Iso-H @ 2002-02-24  2:37 UTC (permalink / raw)
  To: gdb


 Is there any way to step over inline functions 
 when using gdb >= 5.1 ? Some (commandline or other)option 
 perhaps?

 gdb-5.0 works as expected, but now I have problem
 with gcc >= 3.x because gdb-5.0 won't work with binaries
 compiled by gcc-3.x; when I start gdb, it only says:

    ...Dwarf Error: Cannot handle DW_FORM_strp in DWARF reader.

 And if I use gdb-5.1 (/gdb-5.1-20020124) it shows
 internals of inline-functions which is really annoying,
 turning gdb-5.1 to almost useless tool!

 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.

-- 

Iso-H



^ permalink raw reply	[flat|nested] 14+ messages in thread

end of thread, other threads:[~2002-08-19 15:48 UTC | newest]

Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2002-02-24  5:14 gdb-5.x and step over inline functions 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
  -- 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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox