This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: hbreak.exp: Test hardware breakpoints
- From: Daniel Jacobowitz <drow at false dot org>
- To: "Maciej W. Rozycki" <macro at mips dot com>
- Cc: gdb-patches at sourceware dot org, "Maciej W. Rozycki" <macro at linux-mips dot org>
- Date: Fri, 21 Sep 2007 19:01:33 -0400
- Subject: Re: hbreak.exp: Test hardware breakpoints
- References: <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