From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25208 invoked by alias); 29 Apr 2009 21:06:52 -0000 Received: (qmail 25198 invoked by uid 22791); 29 Apr 2009 21:06:51 -0000 X-SWARE-Spam-Status: No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: sourceware.org Received: from mx2.redhat.com (HELO mx2.redhat.com) (66.187.237.31) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Wed, 29 Apr 2009 21:06:45 +0000 Received: from int-mx2.corp.redhat.com (int-mx2.corp.redhat.com [172.16.27.26]) by mx2.redhat.com (8.13.8/8.13.8) with ESMTP id n3TL4hs2002865; Wed, 29 Apr 2009 17:04:43 -0400 Received: from ns3.rdu.redhat.com (ns3.rdu.redhat.com [10.11.255.199]) by int-mx2.corp.redhat.com (8.13.1/8.13.1) with ESMTP id n3TL4fRJ000603; Wed, 29 Apr 2009 17:04:42 -0400 Received: from opsy.redhat.com (vpn-13-28.rdu.redhat.com [10.11.13.28]) by ns3.rdu.redhat.com (8.13.8/8.13.8) with ESMTP id n3TL4ea2014249; Wed, 29 Apr 2009 17:04:41 -0400 Received: by opsy.redhat.com (Postfix, from userid 500) id 8EB48888034; Wed, 29 Apr 2009 15:04:39 -0600 (MDT) To: Pedro Alves Cc: gdb-patches@sourceware.org Subject: Re: Fix 'catch catch' crash References: <200904292035.17446.pedro@codesourcery.com> From: Tom Tromey Reply-To: tromey@redhat.com Date: Wed, 29 Apr 2009 21:06:00 -0000 In-Reply-To: <200904292035.17446.pedro@codesourcery.com> (Pedro Alves's message of "Wed\, 29 Apr 2009 20\:35\:17 +0100") Message-ID: User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.2 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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: 2009-04/txt/msg00798.txt.bz2 >>>>> "Pedro" == Pedro Alves writes: Pedro> (gdb) catch catch Pedro> Function "__cxa_begin_catch" not defined. Pedro> The nagging about not finding the "__cxa_begin_catch" function Pedro> could be hidden from the user; Yeah... would you mind filing a bug report for this? (And for the other too, if you want; this one seemed more important to me somehow.) thanks, Tom