From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 3890 invoked by alias); 4 Oct 2011 15:43:11 -0000 Received: (qmail 3879 invoked by uid 22791); 4 Oct 2011 15:43:09 -0000 X-SWARE-Spam-Status: No, hits=-7.2 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; Tue, 04 Oct 2011 15:42:55 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p94FgtJe025207 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Tue, 4 Oct 2011 11:42:55 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id p94FgsAH003187; Tue, 4 Oct 2011 11:42:54 -0400 Received: from barimba (ovpn01.gateway.prod.ext.phx2.redhat.com [10.5.9.1]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id p94Fgrqc015239; Tue, 4 Oct 2011 11:42:53 -0400 From: Tom Tromey To: Paul Koning Cc: pmuldoon@redhat.com, gdb-patches@sourceware.org Subject: Re: Python: fetch value when building gdb.Value object References: <36B29E9D-F2B3-446F-AF8A-97254A3AAEE2@comcast.net> Date: Tue, 04 Oct 2011 15:43:00 -0000 In-Reply-To: (Paul Koning's message of "Wed, 28 Sep 2011 15:48:21 -0400") Message-ID: User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.50 (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: 2011-10/txt/msg00086.txt.bz2 >>>>> "Paul" == Paul Koning writes: Paul> The first of those two has a traceback because the gdb.Value Paul> arithmetic operations have a TRY_CATCH in them. The second one Paul> has no traceback because the "nonzero" method of gdb.Value doesn't Paul> do TRY_CATCH. It is a bug that nonzero doesn't use TRY_CATCH. In the Python-facing code, the rule is that any calls into gdb proper which may throw must be wrapped in TRY_CATCH and then must have exception-conversion code, usually just GDB_PY_HANDLE_EXCEPTION. This rule is needed to interface properly between gdb exceptions (which longjmp) and Python exceptions (which do not). Omitting it can lead, I believe, to crashes. Tom