From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: asmwarrior <asmwarrior@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Why running the next command will jump back to the previous line position
Date: Sat, 29 Oct 2011 10:39:00 -0000 [thread overview]
Message-ID: <20111029074921.GA11261@host1.jankratochvil.net> (raw)
In-Reply-To: <4EABAF25.7060605@gmail.com>
On Sat, 29 Oct 2011 09:45:41 +0200, asmwarrior wrote:
> When leaving the main function body, the instruction piece of the destructor
> will reached, and gdb just refer to the declaration line. So that gdb put
> the current source line back to "std::map<int, std::string> m;" again.
>
> My explanation is right?
yes.
> I'm not quite sure what DW_LNS_negate_stmt means, any way, I will forward my
> question to GCC maillist.
DWARF:
is_stmt
A boolean indicating that the current instruction is a recommended breakpoint
location. A recommended breakpoint location is intended to “represent” a line,
a statement and/or a semantically distinct subpart of a statement.
I am not convinced myself it is right to hide destructor calls; but I am not
C++ developer.
Regards,
Jan
next prev parent reply other threads:[~2011-10-29 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 7:23 asmwarrior
2011-10-29 7:42 ` Jan Kratochvil
2011-10-29 7:49 ` asmwarrior
2011-10-29 10:39 ` Jan Kratochvil [this message]
2011-10-29 14:14 ` 陳韋任
2011-10-29 17:12 ` asmwarrior
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=20111029074921.GA11261@host1.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=asmwarrior@gmail.com \
--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