From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22710 invoked by alias); 29 Jan 2003 08:10:30 -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 22689 invoked from network); 29 Jan 2003 08:10:30 -0000 Received: from unknown (HELO buffy.herge.org) (81.56.139.128) by 172.16.49.205 with SMTP; 29 Jan 2003 08:10:30 -0000 Received: by buffy.herge.org (Postfix, from userid 1000) id AECD883EC3; Wed, 29 Jan 2003 09:10:28 +0100 (CET) Date: Wed, 29 Jan 2003 08:10:00 -0000 From: Romain Guilleret To: gdb@sources.redhat.com Subject: debugging assembler instructions Message-ID: <20030129081028.GB1976@buffy.herge.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i X-Operating-System: DEBIAN/GNU Linux 2.4.19 woody on an i686 X-SW-Source: 2003-01/txt/msg00477.txt.bz2 Hi, I've written assembler code using __asm__. The code does not work as expected and I would like to debug it. Is it possible to do so using GDB ? Ideally, I would like gdb to stop after every assembler instruction so that I can inspect memory or registers to find what's wrong. Is it possible to do so using GDB ? If not, does anybody know another tool that could do it ? I'm using GDB 5.2 on a Debian woody system. TIA Romain Guilleret