From: ikorot@earthlink.net
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Novice gdb question
Date: Fri, 03 Jul 2009 20:04:00 -0000 [thread overview]
Message-ID: <13160568.1246651456509.JavaMail.root@mswamui-blood.atl.sa.earthlink.net> (raw)
Hi, ALL
When I try to debug a program that has inline function (C++) with gdb
and MSVC debugger I get an incnsistent behavior.
Scenario:
I am stepping in the function that is inline:
class Foo
{
void inlineFunc( int param ) { m_member = param; };
void nonInlineFunc();
private:
int m_member;
};
Calling code:
Foo f;
...........
f.inlineFunc( 5 );
f.noninlineFunc();
Then I hit next.
Result:
In MSVC debugger, when I hit next standing on the inline function call
I will end up on the line "f.inlineFunc( 5 );"
In gdb when I hit next standing on the inline function call I will end up
on the line "f.noninlineFunc();"
Is it possible to make gdb aware of the inline-ness and make it work as MSVC
debugger?
Thank you.
next reply other threads:[~2009-07-03 20:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-03 20:04 ikorot [this message]
2009-07-03 22:15 ` Daniel Jacobowitz
2009-07-05 0:19 ` Paul Pluzhnikov
2009-07-06 3:11 ikorot
2009-07-06 3:26 ` Paul Pluzhnikov
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=13160568.1246651456509.JavaMail.root@mswamui-blood.atl.sa.earthlink.net \
--to=ikorot@earthlink.net \
--cc=gdb@sourceware.org \
/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