public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: <gdb-patches@sourceware.org>
Cc: Terry Guo <flameroc@gmail.com>, <gdb@sourceware.org>
Subject: Re: Hardware breakpoint limitation issue during the gdb regression test
Date: Thu, 09 Aug 2012 03:48:00 -0000	[thread overview]
Message-ID: <2908402.0pCVQUbaGe@qiyao.dyndns.org> (raw)
In-Reply-To: <CAGbRaL4uR0MZJHwre7j16ybiEViO5ChRp8QXa4HTEDz9ikiT2A@mail.gmail.com>

On Wednesday, August 08, 2012 04:55:44 PM Terry Guo wrote:
> I managed to run gdb "make check" on a real arm cortex-m3 board.
> During this regression test, I saw many failures are caused by "Cannot
> insert hardware breakpoint 8" and "You may have requested too many
> hardware breakpoints/watchpoints". It's true that my arm board only
> supports limited number breakpoints. So how to workaround this
> limitation for regression test? Thanks.

You don't have to workaround this limitation.  x86 also has a limited number 
of hardware breakpoints and processor with unlimited hw breakpoints doesn't 
exist at all :)  If testsuite works for x86, it should work for your 
configuration.

As you provide quite few information, I can't tell where the problem is.  In 
testsuite, it is regarded that target "arm*-*-*" supports both hardware 
breakpoint and watchpoint (see skip_hw_breakpoint_tests and 
skip_hw_watchpoint_tests in testsuite/lib/gdb.exp), so all hw watch/break 
tests are run on your board.

You have to check whether your stub is able to handle hardware 
breakpoint/watchpoint packets, and insert them correctly.

-- 
Yao (齐尧)

  parent reply	other threads:[~2012-08-09  3:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08  8:55 Terry Guo
2012-08-08 16:40 ` Liang Cheng
2012-08-09  0:03 ` Luis Gustavo
2012-08-09  3:48 ` Yao Qi [this message]
2012-08-09  9:12   ` Terry Guo
2012-08-09 10:30     ` Mark Kettenis
2012-08-09 10:42       ` Jan Kratochvil
2012-08-09 16:00         ` Eli Zaretskii

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=2908402.0pCVQUbaGe@qiyao.dyndns.org \
    --to=yao@codesourcery.com \
    --cc=flameroc@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).