From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12243 invoked by alias); 6 Feb 2013 20:00:59 -0000 Received: (qmail 12233 invoked by uid 22791); 6 Feb 2013 20:00:58 -0000 X-SWARE-Spam-Status: No, hits=-6.4 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_SPAMHAUS_DROP,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 06 Feb 2013 20:00:52 +0000 Received: from int-mx12.intmail.prod.int.phx2.redhat.com (int-mx12.intmail.prod.int.phx2.redhat.com [10.5.11.25]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r16K0l7f015981 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 6 Feb 2013 15:00:49 -0500 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx12.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r16K0O0v023874 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Wed, 6 Feb 2013 15:00:38 -0500 From: Tom Tromey To: Siva Chandra Cc: Doug Evans , gdb-patches@sourceware.org Subject: Re: [RFC - Python Scripting] New method gdb.Architecture.disassemble References: <20753.38272.55066.651097@ruffy2.mtv.corp.google.com> Date: Wed, 06 Feb 2013 20:00:00 -0000 In-Reply-To: (Siva Chandra's message of "Tue, 5 Feb 2013 17:53:01 -0800") Message-ID: <87txppw6uf.fsf@fleche.redhat.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.92 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain Mailing-List: contact gdb-patches-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-patches-owner@sourceware.org X-SW-Source: 2013-02/txt/msg00162.txt.bz2 >>>>> "Siva" == Siva Chandra writes: Siva> The only useful entry point currently available is gdb_disassembly and Siva> I do not think it is a bad entry point. Other disassembly functions in Siva> disasm.c are static. However, for the Python API, my patch provides Siva> only one option of whether to include or exclude opcodes in the Siva> disassembled output. Come to think of it, why have that knob at all? It is easy enough to ignore fields in structured output. Tom