From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 27336 invoked by alias); 29 Oct 2011 14:14:21 -0000 Received: (qmail 27326 invoked by uid 22791); 29 Oct 2011 14:14:18 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_DB,TW_NW X-Spam-Check-By: sourceware.org Received: from mail-iy0-f169.google.com (HELO mail-iy0-f169.google.com) (209.85.210.169) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Sat, 29 Oct 2011 14:14:05 +0000 Received: by iagf6 with SMTP id f6so6949535iag.0 for ; Sat, 29 Oct 2011 07:14:04 -0700 (PDT) Received: by 10.43.52.136 with SMTP id vm8mr10505511icb.26.1319897643562; Sat, 29 Oct 2011 07:14:03 -0700 (PDT) Received: from [192.168.1.102] ([115.195.154.122]) by mx.google.com with ESMTPS id bu33sm17247808ibb.11.2011.10.29.07.12.57 (version=SSLv3 cipher=OTHER); Sat, 29 Oct 2011 07:14:02 -0700 (PDT) Message-ID: <4EAC0A9F.3080709@gmail.com> Date: Sat, 29 Oct 2011 17:12:00 -0000 From: asmwarrior User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:7.0.1) Gecko/20110929 Thunderbird/7.0.1 MIME-Version: 1.0 To: Jan Kratochvil , gdb@sourceware.org Subject: Re: Why running the next command will jump back to the previous line position References: <4EABA71D.600@gmail.com> <20111029072237.GA3977@host1.jankratochvil.net> <4EABAF25.7060605@gmail.com> <20111029103901.GA36577@cs.nctu.edu.tw> In-Reply-To: <20111029103901.GA36577@cs.nctu.edu.tw> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Mailing-List: contact gdb-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sourceware.org X-SW-Source: 2011-10/txt/msg00215.txt.bz2 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