From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29857 invoked by alias); 11 Oct 2012 12:25:07 -0000 Received: (qmail 29827 invoked by uid 22791); 11 Oct 2012 12:25:04 -0000 X-SWARE-Spam-Status: No, hits=-5.5 required=5.0 tests=BAYES_00,KHOP_THREADED,RP_MATCHES_RCVD,SPF_HELO_PASS X-Spam-Check-By: sourceware.org Received: from plane.gmane.org (HELO plane.gmane.org) (80.91.229.3) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 11 Oct 2012 12:24:59 +0000 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1TMHp1-0004S4-Pv for binutils@sources.redhat.com; Thu, 11 Oct 2012 14:25:03 +0200 Received: from HSI-KBW-46-237-199-196.hsi.kabel-badenwuerttemberg.de ([46.237.199.196]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 11 Oct 2012 14:25:03 +0200 Received: from gpiasenza by HSI-KBW-46-237-199-196.hsi.kabel-badenwuerttemberg.de with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 11 Oct 2012 14:25:03 +0200 To: binutils@sources.redhat.com From: Guido Piasenza Subject: Re: Strange ARM issue: wrong exception table type? Date: Thu, 11 Oct 2012 12:25:00 -0000 Message-ID: References: <35a37ea957466b2f7a770e7978aebfef.squirrel@localhost> <20120202104445.GF392@e103070-lin.arm.com> <098d5826f7b6f8520ee6b9359e939f87.squirrel@localhost> <20120202170702.GA2544@e103070-lin.arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit User-Agent: Loom/3.14 (http://gmane.org/) X-IsSubscribed: yes Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org X-SW-Source: 2012-10/txt/msg00133.txt.bz2 I also saw this problem, arm-gcc on my machine spits out code which can't catch exceptions, whereas the very same compiler on a colleague's machine works perfectly. I eventually found out that this is triggered by these environment variables on my machine: MALLOC_CHECK_=3 MALLOC_PERTURB_=69 without these variables I can compile nicely. So I'd say there is a bug in arm-gcc which is just waiting to show up, and MALLOC_PERTURB_ makes it come out from the shadows. Other conditions might trigger the same problem, but for the time being I unset these variables and hope for the best. Guido