From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26811 invoked by alias); 2 Dec 2004 09:15:18 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 26714 invoked from network); 2 Dec 2004 09:15:06 -0000 Received: from unknown (HELO alice.acmet.com) (61.11.104.17) by sourceware.org with SMTP; 2 Dec 2004 09:15:06 -0000 Received: from u8test4 (localhost [127.0.0.1] (may be forged)) by alice.acmet.com (8.11.6/8.11.6) with ESMTP id iB29Pgo10675; Thu, 2 Dec 2004 14:55:42 +0530 From: "Tarun" To: Cc: , "Ms.Ranjeeta" , "rm@acmet.com" Subject: Query regarding assembly level debugging support Date: Thu, 02 Dec 2004 09:15:00 -0000 Message-ID: <000e01c4d84f$dba18c30$a100a8c0@u8test4> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-SW-Source: 2004-12/txt/msg00008.txt.bz2 Hi All, I am generating object file in Elf/Dwarf format. The prime target is to be able to debug the assembly code. That is we are able to step through the assembly code showing line numbers and relative addresses. The Dwarf (version 2.0) sections currently being included are - debug_line - debug_abbrev - debug_info. The linked out file is loaded without errors on GDB. When we run the respective out file on GDB, the control of debugger moves to label main in the assembly code ( Breakpoint 1, 0xa00200ec in main ()). When I try to move to next instruction using "nexti", the control moves to next address (Displaying: 0xa00200f0 in main ()). This continues till the last address is reached. Only the address increments within the assembly file are displayed and not the actual assembly source. When I try to single step using "step", the message prompted is "Single stepping until exit from function main, which has no line number information". Whereas if I disassemble one of the addresses give above, entire assembly code which I am trying to debug is displayed. Does this mean that GDB does not support debugging of the assembly code? Regards, Tarun