From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 58268 invoked by alias); 8 Feb 2017 12:06:09 -0000 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 Received: (qmail 58258 invoked by uid 89); 8 Feb 2017 12:06:08 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-0.0 required=5.0 tests=BAYES_40,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=nitish, Nitish, kumar, Kumar X-HELO: mx1.redhat.com Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 08 Feb 2017 12:06:07 +0000 Received: from int-mx10.intmail.prod.int.phx2.redhat.com (int-mx10.intmail.prod.int.phx2.redhat.com [10.5.11.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 299FF1555A; Wed, 8 Feb 2017 12:06:07 +0000 (UTC) Received: from [127.0.0.1] (ovpn04.gateway.prod.ext.ams2.redhat.com [10.39.146.4]) by int-mx10.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id v18C64FR018731; Wed, 8 Feb 2017 07:06:05 -0500 Subject: Re: Issue with Latest GDB on AIX with GCC-6.12 To: Nitish Kumar Mishra , David Edelsohn References: <21a21388-b1d9-816c-377e-d4e084cc399e@redhat.com> <331a72d9-050c-7cd7-adc2-78e5f1ed6f85@redhat.com> <57147db4-83c3-2a8f-0c74-0efc6a94e9f5@redhat.com> Cc: "gdb@sourceware.org" , Yao Qi From: Pedro Alves Message-ID: Date: Wed, 08 Feb 2017 12:06:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-SW-Source: 2017-02/txt/msg00014.txt.bz2 On 02/08/2017 06:16 AM, Nitish Kumar Mishra wrote: > I tried adding try/catch block earlier in throw_it and > throw_exception_cxx functions > but got no significant results. > I had tried adding try catch block in these functions: > kill_command > command_handler > command_line_handler > execute_command > throw_it > throw_exception_cxx, > but no progress. Output is exactly same as we got earlier (Other than > extra frames for new > try catch functions). None of the print statements in catch blocks for > above functions worked. Eh, it sounds like _no_ exception catching works then? I just confirmed now that at least on GNU/Linux, GDB does not throw any exception internally during startup. This backtrace in question may well not be special at all, and may be that _all_ exception catching is broken. I'd try experimenting with simple things like: try { throw 1; } catch (...) { printf (....); } right at the start of gdb's main(). Not in a separately compiled test program, but really inside gdb, to avoid differences in how gdb vs the test program is built. It could also be that this is only triggered due to GDB's binary size, hence not triggered in a small program -- I recall that there was some trouble with the size of some sessions and the linker in the AIX 7.1 box couldn't link gdb, or something like that? Maybe that's not fully/correctly sorted out. Thanks, Pedro Alves