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 10:09:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.21.0202241954580.16535-100000@alphatux2.ts.ray.fi> (raw)
In-Reply-To: <Pine.LNX.4.21.0202241923190.16535-100000@alphatux2.ts.ray.fi>
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 ;)
---------------------------------------------------------------
#include <stdio.h>
#include <sys/types.h>
class Demo_t
{
public:
inline Demo_t(int32_t);
inline int32_t m_demomethod(int32_t);
private:
int32_t a_1;
int32_t a_2;
};
Demo_t::Demo_t(int32_t p_arg)
{
a_1 = p_arg;
a_2 = 0;
}
int32_t Demo_t::m_demomethod(
int32_t p_arg
)
{
return a_1 + p_arg;
}
int f_func( int32_t p_arg);
//###############################################
int
main(
int32_t p_argc,
int8_t** pp_argv
)
{
printf("value: %d\n", f_func(2));
}
//###############################################
int
f_func(
int32_t p_arg
)
{
Demo_t a(1);
printf("value: %d\n", a.m_demomethod(2));
}
---------------------------------------------------------------
and compiling command is:
g++ -O2 -g3 gdb-5.x-inline-test.cxx -o test.bin
And here is gdb session:
-------------------------------------------------------
#gdb test.bin
GNU gdb 20020124
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License,
and you are welcome to change it and/or distribute copies of it
under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for
details.
This GDB was configured as "alphaev56-unknown-linux-gnu"...
(gdb) list f_func
12 int32_t a_1;
13 int32_t a_2;
14 };
15
16 Demo_t::Demo_t(int32_t p_arg)
17 {
18 a_1 = p_arg;
19 a_2 = 0;
20 }
21
(gdb) q
#
-------------------------------------------------------
As you can see, gdb doesn't show "f_func", but Demo_t's
constructor instead !
There is also some variation; if constructor's "p_arg" parameter
is removed then list dump is correct!?
>
> >
> >
>
>
--
Iso-H
next prev parent reply other threads:[~2002-02-24 18:09 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 [this message]
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.0202241954580.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