From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15525 invoked by alias); 12 Oct 2011 15:28:49 -0000 Received: (qmail 15513 invoked by uid 22791); 12 Oct 2011 15:28:48 -0000 X-SWARE-Spam-Status: No, hits=-6.7 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,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, 12 Oct 2011 15:28:30 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p9CFSPDv012011 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 12 Oct 2011 11:28:25 -0400 Received: from localhost.localdomain (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p9CFSOc9028075; Wed, 12 Oct 2011 11:28:24 -0400 From: Phil Muldoon To: Kevin Pouget Cc: Pedro Alves , gdb-patches@sourceware.org Subject: Re: [RFC][Python] gdbpy_frame_stop_reason_string bug References: <201110121552.29096.pedro@codesourcery.com> Reply-to: pmuldoon@redhat.com X-URL: http://www.redhat.com Date: Wed, 12 Oct 2011 15:28:00 -0000 In-Reply-To: (Kevin Pouget's message of "Wed, 12 Oct 2011 17:17:32 +0200") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-IsSubscribed: yes 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: 2011-10/txt/msg00356.txt.bz2 Kevin Pouget writes: > it looks like these enums are not documented, are they? I can't grep > 'FRAME_UNWIND_NO_REASON' in gdb.texinfo Yeah, that at least is a bug for sure. > ('2' was a bad example, but the reason why I first used '0' was > because it was returned by Frame.unwind_stop_reason(), as depicted in > the first mail) > by the way, python print > gdb.frame_stop_reason_string(gdb.FRAME_UNWIND_FIRST_ERROR) crashes the > same way, there is certainly a few more lines to fix on the Python > side I can look at this, or you can hack on it. I don't mind. Cheers, Phil