From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15385 invoked by alias); 3 Nov 2004 00:48:21 -0000 Mailing-List: contact gdb-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: gdb-owner@sources.redhat.com Received: (qmail 15374 invoked from network); 3 Nov 2004 00:48:20 -0000 Received: from unknown (HELO pippin.tausq.org) (64.81.244.94) by sourceware.org with SMTP; 3 Nov 2004 00:48:20 -0000 Received: by pippin.tausq.org (Postfix, from userid 1000) id 51288CE341; Tue, 2 Nov 2004 16:48:26 -0800 (PST) Date: Wed, 03 Nov 2004 00:48:00 -0000 From: Randolph Chung To: Joel Brobecker Cc: gdb@sources.redhat.com Subject: Re: Unwinding past main Message-ID: <20041103004826.GY4249@tausq.org> Reply-To: Randolph Chung References: <20041102232929.GW4249@tausq.org> <20041103001452.GA986@gnat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041103001452.GA986@gnat.com> X-GPG: for GPG key, see http://www.tausq.org/gpg.txt User-Agent: Mutt/1.5.5.1+cvs20040105i X-SW-Source: 2004-11/txt/msg00023.txt.bz2 > Funny you would see that. I am just looking at the same sort of > problem, but on IA64. I have an infinite loop when unwinding the > call stack from a thread. I don't understand all the conditions > yet (I am completely new to IA64, and it's quite complex for me). oh, it used to do this on hppa too... we unwind to the clone call and then it gets all confused. > So you are right in saying that this can happen on other targets too. > In my case, the "main" is the NPTL thread start routine, and we try > to unwind past it. In some cases, we are lucky, because we end up > with 2 identical frames which cause an error, but in some others, > the frame base changes slightly from frame to frame and we loop... yup. that's what i see too in this case. randolph -- Randolph Chung Debian GNU/Linux Developer, hppa/ia64 ports http://www.tausq.org/