From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14018 invoked by alias); 28 Jun 2011 13:22:54 -0000 Received: (qmail 14007 invoked by uid 22791); 28 Jun 2011 13:22:53 -0000 X-SWARE-Spam-Status: No, hits=-2.6 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW X-Spam-Check-By: sourceware.org Received: from mail-ww0-f43.google.com (HELO mail-ww0-f43.google.com) (74.125.82.43) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 28 Jun 2011 13:22:38 +0000 Received: by wwi18 with SMTP id 18so160288wwi.12 for ; Tue, 28 Jun 2011 06:22:37 -0700 (PDT) Received: by 10.227.55.66 with SMTP id t2mr6546828wbg.109.1309267357267; Tue, 28 Jun 2011 06:22:37 -0700 (PDT) Received: from 1n450.cable.virginmedia.net (cpc3-cmbg12-0-0-cust651.5-4.cable.virginmedia.com [86.9.126.140]) by mx.google.com with ESMTPS id en1sm160838wbb.1.2011.06.28.06.22.35 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 28 Jun 2011 06:22:36 -0700 (PDT) Date: Tue, 28 Jun 2011 13:22:00 -0000 From: Catalin Marinas To: Russell King - ARM Linux Cc: Hui Zhu , Dmitry Eremin-Solenikov , Yao Qi , Eric Miao , linux-arm-kernel@lists.infradead.org, gdb@sourceware.org Subject: Re: Problem with GDB when debugging IRQ handlers Message-ID: <20110628132407.GB7255@1n450.cable.virginmedia.net> References: <20110627125306.GA30646@doriath.ww600.siemens.net> <20110627132735.GE16103@n2100.arm.linux.org.uk> <4E088DE1.2060809@gmail.com> <4E089AB3.1090801@codesourcery.com> <20110628103946.GC21898@n2100.arm.linux.org.uk> <20110628120928.GD21898@n2100.arm.linux.org.uk> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20110628120928.GD21898@n2100.arm.linux.org.uk> User-Agent: Mutt/1.5.20 (2009-06-14) 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: 2011-06/txt/msg00156.txt.bz2 On Tue, Jun 28, 2011 at 01:09:28PM +0100, Russell King - ARM Linux wrote: > On Tue, Jun 28, 2011 at 08:06:27PM +0800, Hui Zhu wrote: > > If this kernel didn't open FRAME_POINTER, what will happen? > > I can't answer that question directly, as I don't use a toolchain new > enough to generate proper unwind information. > > However, I haven't seen any problems being reported on the list with > bad/broken backtraces from the kernel, so my _assumption_ is that the > kernel is fine with its own debug info. I tested this when contributing the unwinding support and it was ok. The reason is that the svc_entry macro in entry-armv.S adds some annotations line .fnstart and .save that generate the correct unwinding bytecodes (but as I said, that's different from the dwarf information which probably needs different annotations). -- Catalin