From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 32499 invoked by alias); 13 Jul 2008 19:47:52 -0000 Received: (qmail 32489 invoked by uid 22791); 13 Jul 2008 19:47:51 -0000 X-Spam-Check-By: sourceware.org Received: from nf-out-0910.google.com (HELO nf-out-0910.google.com) (64.233.182.190) by sourceware.org (qpsmtpd/0.31) with ESMTP; Sun, 13 Jul 2008 19:47:27 +0000 Received: by nf-out-0910.google.com with SMTP id h3so1368606nfh.48 for ; Sun, 13 Jul 2008 12:47:24 -0700 (PDT) Received: by 10.210.92.11 with SMTP id p11mr8354589ebb.175.1215978444250; Sun, 13 Jul 2008 12:47:24 -0700 (PDT) Received: by 10.210.66.15 with HTTP; Sun, 13 Jul 2008 12:47:24 -0700 (PDT) Message-ID: <6dc9ffc80807131247y7a85d860ga3df0fb6fa23e977@mail.gmail.com> Date: Sun, 13 Jul 2008 19:47:00 -0000 From: "H.J. Lu" To: "Craig Silverstein" Subject: Re: inflateInit? Cc: hp@bitrange.com, drow@false.org, dj@redhat.com, binutils@sourceware.org, gdb@sourceware.org In-Reply-To: <20080713193347.DF0453F305E@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20080710165155.D15CA3F3058@localhost> <200807101923.m6AJNZBw006371@greed.delorie.com> <20080710201210.GA11942@caradoc.them.org> <20080710203453.4A7333F3058@localhost> <20080710180821.T66839@dair.pair.com> <20080711005501.4CF353F3058@localhost> <6dc9ffc80807121128r2abd2efgd519876c331ef024@mail.gmail.com> <20080712193648.72DEA3F305D@localhost> <6dc9ffc80807130857u7c8f72ffvbe53c8dfd376229d@mail.gmail.com> <20080713193347.DF0453F305E@localhost> 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 X-SW-Source: 2008-07/txt/msg00145.txt.bz2 On Sun, Jul 13, 2008 at 12:33 PM, Craig Silverstein wrote: > } Your patch caused another regression: > } http://sourceware.org/bugzilla/show_bug.cgi?id=6743 > } Could you please fix it? > > I'll look into it now. Sorry for the trouble. If you can come up > with a simple testcase that tests this (I had trouble coming up with a > good addr2line test, since results are so architecture dependent), > I'll add it to the testsuite so something like this doesn't happen > again. > Here is one: ./addr2line -e ./addr2line `nm -n --defined-only ./addr2line |head -1 | awk '{print $1}'` But it may not abort on all platforms. -- H.J.