From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25400 invoked by alias); 3 Nov 2004 00:14:55 -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 25385 invoked from network); 3 Nov 2004 00:14:53 -0000 Received: from unknown (HELO takamaka.act-europe.fr) (142.179.108.108) by sourceware.org with SMTP; 3 Nov 2004 00:14:53 -0000 Received: by takamaka.act-europe.fr (Postfix, from userid 507) id 230F947D9F; Tue, 2 Nov 2004 16:14:52 -0800 (PST) Date: Wed, 03 Nov 2004 00:14:00 -0000 From: Joel Brobecker To: Randolph Chung Cc: gdb@sources.redhat.com Subject: Re: Unwinding past main Message-ID: <20041103001452.GA986@gnat.com> References: <20041102232929.GW4249@tausq.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20041102232929.GW4249@tausq.org> User-Agent: Mutt/1.4i X-SW-Source: 2004-11/txt/msg00022.txt.bz2 > I'm seeing a stack unwinding problem on hppa. Seems like this should be > applicable to other targets too -- how do you solve this problem? 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). 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... -- Joel