public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: asmwarrior <asmwarrior@gmail.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb@sourceware.org
Subject: Re: Why running the next command will jump back to the previous line position
Date: Sat, 29 Oct 2011 17:12:00 -0000	[thread overview]
Message-ID: <4EAC0A9F.3080709@gmail.com> (raw)
In-Reply-To: <20111029103901.GA36577@cs.nctu.edu.tw>

On 2011-10-29 18:39, 陳韋任 wrote:
>>> Maybe GCC could produce there DW_LNS_negate_stmt so that the variable
>>> declaration line is still shown in backtraces (if the destructor crashes) but
>>> it is skipped over during stepping/nexting; but GDB currently would not show
>>> such line in backtraces, GCC currently does not produce DW_LNS_negate_stmt
>>> anyway.
>>>
>>
>> I'm not quite sure what DW_LNS_negate_stmt means, any way, I will forward my question to GCC maillist.
> 
>    GCC should emit debug information so that GDB can work correctly.
> You can checkout http://dwarfstd.org/doc/Dwarf3.pdf .
> 
> Regards,
> chenwj
> 

Well, thanks. It looks like there is a similar gcc bug report.
see:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49951
It looks like at this revision:
http://gcc.gnu.org/viewcvs?view=revision&revision=149722

I have no experience to dig into gcc source.... Hope the GCC guys can help.

asmwarrior
ollydbg from codeblocks' forum

      reply	other threads:[~2011-10-29 14:14 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
2011-10-29 14:14     ` 陳韋任
2011-10-29 17:12       ` asmwarrior [this message]

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=4EAC0A9F.3080709@gmail.com \
    --to=asmwarrior@gmail.com \
    --cc=gdb@sourceware.org \
    --cc=jan.kratochvil@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).