From: Daniel Jacobowitz <drow@false.org>
To: "Maciej W. Rozycki" <macro@mips.com>
Cc: gdb-patches@sourceware.org, "Maciej W. Rozycki" <macro@linux-mips.org>
Subject: Re: hbreak.exp: Test hardware breakpoints
Date: Fri, 21 Sep 2007 23:01:00 -0000 [thread overview]
Message-ID: <20070921230133.GB28500@caradoc.them.org> (raw)
In-Reply-To: <Pine.LNX.4.61.0709121858320.17380@perivale.mips.com>
On Wed, Sep 12, 2007 at 07:09:39PM +0100, Maciej W. Rozycki wrote:
> Hello,
>
> This is hbreak.exp, a complement to break.exp, derived from same, which
> is meant to test hardware breakpoints as implemented by the "hbreak" and
> "thbreak" commands (which are not covered by the test suite as of now).
> As the number of hardware breakpoints is usually limited the script has
> been modified to only have a single such breakpoint set up at any given
> time.
>
> This script has been tested natively for i386-linux-gnu with all the
> tests passing.
>
> 2007-09-12 Maciej W. Rozycki <macro@mips.com>
>
> * gdb.base/hbreak.exp: New test for "hbreak" and "thbreak".
>
> OK to apply?
No, sorry. Compare this to the current break.exp - you'll see
that it has some cruft that was cleaned out of that testcase, like
gdb_suppress_entire_file.
Also, when I try it using gdbserver it fails a lot of tests. This
is at least partially related to the previous problem (gdb_run_cmd
was added). I wanted to see what happened on a target that only
failed to insert hardware breakpoints at continue.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-09-21 23:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-12 18:10 Maciej W. Rozycki
2007-09-21 23:01 ` Daniel Jacobowitz [this message]
2007-09-24 11:23 ` Maciej W. Rozycki
2007-09-24 11:32 ` Daniel Jacobowitz
2007-09-26 14:03 ` Maciej W. Rozycki
2007-09-26 14:21 ` Daniel Jacobowitz
2007-09-26 14:25 ` Maciej W. Rozycki
2007-09-26 14:29 ` Pedro Alves
2007-09-26 14:57 ` Maciej W. Rozycki
2007-09-26 15:51 ` Daniel Jacobowitz
2007-09-27 9:58 ` Maciej W. Rozycki
2007-09-27 12:08 ` Daniel Jacobowitz
2007-09-30 1:18 ` Daniel Jacobowitz
2007-10-23 17:10 ` Maciej W. Rozycki
2008-02-27 15:39 ` Maciej W. Rozycki
2008-03-01 4:40 ` Daniel Jacobowitz
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=20070921230133.GB28500@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=macro@linux-mips.org \
--cc=macro@mips.com \
/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