From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 41567 invoked by alias); 12 Feb 2017 23:52:48 -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 41552 invoked by uid 89); 12 Feb 2017 23:52:48 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.9 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=Hx-languages-length:908, IMO, imo, H*f:sk:bsurTz7 X-HELO: mail-wm0-f66.google.com Received: from mail-wm0-f66.google.com (HELO mail-wm0-f66.google.com) (74.125.82.66) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 12 Feb 2017 23:52:46 +0000 Received: by mail-wm0-f66.google.com with SMTP id v77so16486926wmv.0 for ; Sun, 12 Feb 2017 15:52:46 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=7veHP/XVsJHQjcKAEL17PJVkQBVcODfOFsJ/dZeDilw=; b=lGgw/ts3fmSST0kqs3kntrIMcKeOAve5navhd6D46xl0oH3SbhVSdco2xZPOhQP0ts 5vvlmiu6qZxMoZIWrYU60KqD2LTc9J1YBCWKxLIsLNFGwtHamcXtLJcFX3R2Mg0ruVzH 4nv8HjznK2reycz9QCKmovYeIaN+NCIzYDBH+T9e+xMqyKEt9JdrNTOmC5dcqzpkQM7o SW5tyyQsFREfL8pe8gU9nowFtGTZY54F+ZiAJsCmKFtuSJtbjrDqmKwJzZ5WrIX4p3QA T31tntrSt01C7XVrkGhI7Lj1hQizJhXhON9iRd+zRpuC5A8RI5bDYf3oDN08bvXl/xIL WiNg== X-Gm-Message-State: AMke39nMIIPmkLeA9hjNWts7oE7VDMMSCa/kPNVmr0Bzgubnfb+wKnzqSYlVM5D6Z7DqUw== X-Received: by 10.28.155.5 with SMTP id d5mr17258919wme.85.1486943564896; Sun, 12 Feb 2017 15:52:44 -0800 (PST) Received: from [192.168.0.102] ([37.189.166.198]) by smtp.gmail.com with ESMTPSA id k43sm11534691wrc.46.2017.02.12.15.52.43 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 12 Feb 2017 15:52:43 -0800 (PST) Subject: Re: Issue with Latest GDB on AIX with GCC-6.12 To: David Edelsohn , Nitish Kumar Mishra References: <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: <5967c781-4f67-06f2-db34-f4cb3818d603@palves.net> Date: Sun, 12 Feb 2017 23:52: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-IsSubscribed: yes X-SW-Source: 2017-02/txt/msg00028.txt.bz2 On 02/12/2017 09:05 PM, David Edelsohn wrote: > Investigating the exception handling problem with another non-IBM AIX > developer, the problem appears to be that statically linking libgcc > and libstdc++ create two, separate and distinct copies of the unwind > tables. These tables are not merged and the unwinder cannot find the > EH catcher. It's not immediately clear why this worked in GCC 4.8 and > not in GCC 4.9 and later. > > GDB with exception handling should work if libgcc and libstdc++ are > linked as shared libraries. The linking error with GCC 6.1 is cockpit > error. > > Can we disable -static-libgcc and -static-libstdc++ for AIX? Works for me. Those are added by the top level configure. They were originally added for gcc, we just inherited it. Ideally adding those would be controllable with a configure option, IMO. Thanks, Pedro Alves