From: Suraj Sivan <suraj.sivan@gmail.com>
To: gdb@sourceware.org
Subject: [GDB help] Regarding breakpoint support in ARM
Date: Mon, 31 May 2010 07:00:00 -0000 [thread overview]
Message-ID: <AANLkTikxSkkxqmCxt-eYAG6FevYv22awWyY7ztRkcvTV@mail.gmail.com> (raw)
Hi,
I'm working with GDB and custom GDB Server for debugging ARM. The core
is ARM7TDMI-S which has 2 hardware resources for setting breakpoints.
I am using the option "set breakpoint always-inserted on" so that
whenever I set a breakpoint or watcpoint, GDB will put it immediately
rather than waiting for continue command. After setting three
breakpoints(2 software and 1 hardware), if I try to put a 4th hardware
breakpoint GDB will give a warning as below:
Warning:
Cannot insert hardware breakpoint 4.
Could not insert hardware breakpoints:
You may have requested too many hardware breakpoints/watchpoints.
Now if I list the breakpoints using "info b" command, GDB displays as below:
Num Type Disp Enb Address What
1 breakpoint keep y 0x40000010 ../source/armloop.s:8
2 breakpoint keep y 0x40000020 ../source/armloop.s:12
3 hw breakpoint keep y 0x40000030 ../source/armloop.s:16
4 hw breakpoint keep y 0x40000040 ../source/armloop.s:20
Here it is seen that GDB keeps the 4th hardware breakpoint information
in its table. If I give a continue command, GDB will try to put the
4th breakpoint again and gives the same warning as above and gets into
a situation where I have to manually delete the 4th breakpoint to
further continue. Is there an option for GDB to not keep the
information of the particular breakpoint which it gives a warning like
above?
regards
Suraj S
next reply other threads:[~2010-05-31 7:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 7:00 Suraj Sivan [this message]
2010-05-31 9:22 ` paawan oza
2010-05-31 10:25 ` Suraj Sivan
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=AANLkTikxSkkxqmCxt-eYAG6FevYv22awWyY7ztRkcvTV@mail.gmail.com \
--to=suraj.sivan@gmail.com \
--cc=gdb@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox