From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3384 invoked by alias); 8 Nov 2007 01:25:08 -0000 Received: (qmail 3361 invoked by uid 22791); 8 Nov 2007 01:25:07 -0000 X-Spam-Check-By: sourceware.org Received: from mail.sunnorth.com.cn (HELO bjmsw01.sunnorth.com.cn) (124.42.0.200) by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 08 Nov 2007 01:25:03 +0000 Received: from maillog.sunnorth.com.cn (unverified [172.20.10.250]) by bjmsw01.sunnorth.com.cn (Clearswift SMTPRS 5.2.9) with ESMTP id ; Thu, 8 Nov 2007 09:26:47 +0800 Received: from ntns1cn.sunnorth.com.cn (ntns1cn.sunnorth.com.cn [172.20.10.252]) by maillog.sunnorth.com.cn (8.12.10/8.12.10) with ESMTP id lA826YN5016445; Thu, 8 Nov 2007 10:06:34 +0800 In-Reply-To: <20071107191651.GM6729@adacore.com> To: Joel Brobecker Cc: gdb@sourceware.org Subject: Re: Question about Dwarf2 for VLIW processor MIME-Version: 1.0 X-Mailer: Lotus Notes Release 6.5 September 26, 2003 Message-ID: From: wangjiong@sunnorth.com.cn Date: Thu, 08 Nov 2007 01:25:00 -0000 Content-Type: text/plain; charset="US-ASCII" 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: 2007-11/txt/msg00051.txt.bz2 Dear Joel: I am using GDB6.1.1 GDB did not stop at the wrong location now, but I have see that the function: find_pc_line_pc_range (stop_pc, &step_range_start, &step_range_end) didn`t work correctly. when stop_pc is 0x8000035 the returned value of step_range_start and step_range_end is 0x800003c5 and 0x800003cb but they should be 0x800003c5 and 0x800003cf I have found all these are because there is something wrong with the Dwarf2 .debug_line section. Now every instruction has a entry in this section, maybe it should be every c statement. Cause I can not modify compiler or assembler now, So I want to know How can I solve this problem just within GDB. Thanks. Wang Jiong tel:2254 Joel Brobecker 2007-11-08 03:16 To wangjiong@sunnorth.com.cn cc gdb@sourceware.org Subject Re: Question about Dwarf2 for VLIW processor It usually helps to know which version of GDB you are using, just in case we know the problem is already fixed in more recent versions. > so gdb will think the statement "int i=1" is from 0x800003c5 to > 0x800003cb which should be 0x800003c5 to 0x800003cf. > > How should I handle this situation, wish your advice . Can you tell us more about the problem that you have (ie the actual external symptoms)? Does GDB stop at the wrong location after you do a "next"? -- Joel