From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 11526 invoked by alias); 25 Jan 2017 11:12:20 -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 11395 invoked by uid 89); 25 Jan 2017 11:12:16 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.4 required=5.0 tests=BAYES_50,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.2 spammy=fexceptions, gcc-6.12, GCC-6.12, nitish 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, 25 Jan 2017 11:12:15 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) (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 0C4156409A; Wed, 25 Jan 2017 11:12:15 +0000 (UTC) Received: from [127.0.0.1] (ovpn04.gateway.prod.ext.phx2.redhat.com [10.5.9.4]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id v0PBCCd1031318; Wed, 25 Jan 2017 06:12:14 -0500 Subject: Re: Issue with Latest GDB on AIX with GCC-6.12 To: Nitish Kumar Mishra , gdb@sourceware.org References: From: Pedro Alves Message-ID: Date: Wed, 25 Jan 2017 11:12: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-01/txt/msg00045.txt.bz2 On 01/25/2017 10:54 AM, Nitish Kumar Mishra wrote: > Hi, > > The latest community gdb is not working with gcc 6.12, however, it > works expectedly fine with GCC-4.8.5 on AIX platform. What is gcc 6.12 ? > #12 0x000000010007d994 in _ZL23gdb_rl_callback_handlerPc > (rl=0x1100e92b0 "") at event-top.c:213 I only saw C++ frames up to here, and the exception should be caught here. I don't immediately see why that wouldn't be working, though maybe it's the "noexcept"? If you remove that, does it fix it? Maybe we need a level of indirection here too, like in gdb_rl_callback_read_char_wrapper_noexcept / gdb_rl_callback_read_char_wrapper. > We are trying some sample programs using readline library to propagate > exceptions through callback handler just to check if we face any issue > there. We are still working on it, can't say anything for sure. Right, it's known that C++ exceptions can't cross readline (unless built with -fexceptions) See log of commits: 89525768cd08 ("Propagate GDB/C++ exceptions across readline using sj/lj-based TRY/CATCH) 2693a26216c3 ("Fix longjmp across readline w/ --enable-sjlj-exceptions toolchains") But it looks like the mechanism to work around that isn't working for you. > It seems like this is a issue regarding exception propagation as > eventually std::terminate() is getting called. Which also suggests > that some how exceptions thrown is not getting handled properly. Yes. Thanks, Pedro Alves