From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15455 invoked by alias); 22 May 2009 21:44:28 -0000 Received: (qmail 15447 invoked by uid 22791); 22 May 2009 21:44:27 -0000 X-SWARE-Spam-Status: No, hits=-2.4 required=5.0 tests=AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Fri, 22 May 2009 21:44:23 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id 43A552BAB8E; Fri, 22 May 2009 17:44:21 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id aZzfpHq7Odtn; Fri, 22 May 2009 17:44:21 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id 0F8DD2BAB89; Fri, 22 May 2009 17:44:21 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id C11A3F5965; Fri, 22 May 2009 23:44:18 +0200 (CEST) Date: Fri, 22 May 2009 21:44:00 -0000 From: Joel Brobecker To: Toshi Morita Cc: gdb@sourceware.org Subject: Re: Disassemble arbitrary memory with disas? Message-ID: <20090522214418.GA24131@adacore.com> References: <987444.33167.qm@web50611.mail.re2.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <987444.33167.qm@web50611.mail.re2.yahoo.com> User-Agent: Mutt/1.5.18 (2008-05-17) 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: 2009-05/txt/msg00151.txt.bz2 > I'm currently debugging a JIT which dynamically generates code, and > I'd like to disassemble it with the "disas" command in GDB. > > However, since there isn't any symbolic information for the buffer in > which the code is generated, GDB refuses to disassemble. I think that the "x /i" command should work. Have a look at the GDB documentation on the "x" command, it should give you more details about how to use the /something modifiers. -- Joel