From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: ikorot@earthlink.net
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: Novice gdb question
Date: Mon, 06 Jul 2009 03:26:00 -0000 [thread overview]
Message-ID: <8ac60eac0907052026w5cde1414w7c91a0408d8bd10f@mail.gmail.com> (raw)
In-Reply-To: <4933903.1246849878501.JavaMail.root@mswamui-thinleaf.atl.sa.earthlink.net>
On Sun, Jul 5, 2009 at 8:11 PM, <ikorot@earthlink.net> wrote:
> Let me put some clarification on it.
I am afraid your clarifications didn't do much clarification (at least
for me :-(
> Consider following code snippet:
Compiled how? Did the 'inlineGetParam()' actually get inlined?
What does the MSVC disassembly show?
> In MSVC debugger and gdb, when I hit F11 standing on the line "f.Bar(....)", I will
> go to the "f.inilineFunc()" line.
Which are the same line; so your description of behavior you observe
continues to be confusing.
Perhaps if you post *complete* test case, with instructions on how to
build it, with the version of MSVC you used, and then describe what
you see in MSVC (using line numbers instead of ambiguous line
descriptions), then we can tell you whether you'll get the same,
better or worse behavior from the next version of GDB.
P.S. Your using of e-mail account with automatic sender verification
to post your questions is quite annoying (at least to me). If spam is
a real problem for you, perhaps try using Gmail? I get less than 1
spam message a week through.
Cheers,
--
Paul Pluzhnikov
next prev parent reply other threads:[~2009-07-06 3:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-06 3:11 ikorot
2009-07-06 3:26 ` Paul Pluzhnikov [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-07-03 20:04 ikorot
2009-07-03 22:15 ` Daniel Jacobowitz
2009-07-05 0:19 ` 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=8ac60eac0907052026w5cde1414w7c91a0408d8bd10f@mail.gmail.com \
--to=ppluzhnikov@google.com \
--cc=gdb@sourceware.org \
--cc=ikorot@earthlink.net \
/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