This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Problem with GDB when debugging IRQ handlers

From: Russell King - ARM Linux <linux at arm dot linux dot org dot uk>
To: Hui Zhu <teawater at gmail dot com>
Cc: Yao Qi <yao at codesourcery dot com>, Dmitry Eremin-Solenikov <dbaryshkov at gmail dot com>, gdb at sourceware dot org, linux-arm-kernel at lists dot infradead dot org, Eric Miao <eric dot y dot miao at gmail dot com>
Date: Tue, 28 Jun 2011 13:09:28 +0100
Subject: Re: Problem with GDB when debugging IRQ handlers
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> <BANLkTi=zjTerne0VbYq-6NaPBuXcZBDGjA@mail.gmail.com>

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.

Follow-Ups:
- Re: Problem with GDB when debugging IRQ handlers
  - From: Catalin Marinas

References:
- Re: Problem with GDB when debugging IRQ handlers
  - From: Dmitry Eremin-Solenikov
- Re: Problem with GDB when debugging IRQ handlers
  - From: Yao Qi
- Re: Problem with GDB when debugging IRQ handlers
  - From: Russell King - ARM Linux
- Re: Problem with GDB when debugging IRQ handlers
  - From: Hui Zhu

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]