From: lilja.magnus@gmail.com (Magnus Lilja)
To: linux-arm-kernel@lists.infradead.org
Subject: Support for KGDB/gdb data watchpoints in ARM kernel?
Date: Sun, 01 Dec 2013 20:46:19 +0100 [thread overview]
Message-ID: <529B920B.1000200@gmail.com> (raw)
Hi,
I've been trying to use KGDB with gdb to debug an ARM Linux kernel. Setting breakpoints at functions works fine, but
whenever I try to set a data watchpoint to make the debugger/system stop when a certain variable/memory location is
modified gdb says 'Could no insert hardware watchpoint 2.'. Although I don't have any other watchpoints/breakpoints
enabled at this time, unless there's something going on under the hood.
I've tried with Kernel 3.12 on i.MX31 (ARM1136) and i.MX53 (Cortex-A8) using both gdb 7.6.1 compiled from sources and
gdb 7.2 from Sourcery CodeBench 2011.09-70.
Any ideas, comments or RTFMs are welcome to enlighten me!
(gdb) watch *(0x8000d300)
Hardware watchpoint 2: *(0x8000d300)
(gdb) c
Continuing.
Warning:
Could not insert hardware watchpoint 2.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.
(gdb) info b
Num Type Disp Enb Address What
2 hw watchpoint keep y *(0x8000d300)
Regards, Magnus Lilja
reply other threads:[~2013-12-01 19:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=529B920B.1000200@gmail.com \
--to=lilja.magnus@gmail.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.