From: tim.bird@am.sony.com (Tim Bird)
To: linux-arm-kernel@lists.infradead.org
Subject: [Kgdb-bugreport] Anyone used KDB single-stepping on ARM
Date: Tue, 13 Dec 2011 13:56:23 -0800 [thread overview]
Message-ID: <4EE7CA07.2050003@am.sony.com> (raw)
In-Reply-To: <4EE7AA4C.2050605@windriver.com>
On 12/13/2011 11:41 AM, Jason Wessel wrote:
> On 10/12/2011 12:41 PM, Tim Bird wrote:
>> I've tried to use single-stepping ('ss' command) on ARM
>> from KDB, without success.
>>
>> Has anyone done this - is it currently supported on ARM?
>
> It is only supported via patches that are not in the mainline kernel the same is also true of the MIPS architecture.
>
> The last consideration I had taken a look at was to consider using the kprobes for single stepping, assuming kprobes work ok on ARM, vs using emulation of single stepping with breakpoints.
>
> The other possibility for newer arm hardward (v7 and up) is to use the hw_breakpoint API and plumb it into kdb/kgdb via the arch/arm/kernel/kgdb.c. It is probably time to take another look at this now since it was merged to the mainline in the last year.
OK. Thanks very much for the response. I started looking at it myself,
and it looked too complicated for me to tackle without a lot
more research. My understanding is that older ARM hardware
(pre-V7) doesn't have single-step support, which appears
to match what you're saying above.
If you or someone else works on this, let me know. I'd be a willing
tester. But I probably don't have enough cycles (or experience with kdb/kgdb)
to actually implement this myself.
-- Tim
=============================
Tim Bird
Architecture Group Chair, CE Workgroup of the Linux Foundation
Senior Staff Engineer, Sony Network Entertainment
=============================
prev parent reply other threads:[~2011-12-13 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-12 17:41 Anyone used KDB single-stepping on ARM Tim Bird
2011-12-13 19:41 ` [Kgdb-bugreport] " Jason Wessel
2011-12-13 21:56 ` Tim Bird [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EE7CA07.2050003@am.sony.com \
--to=tim.bird@am.sony.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.