Re: hbreak.exp: Test hardware breakpoints

["Maciej W. Rozycki" <macro@mips.com>]

On Wed, 26 Sep 2007, Pedro Alves wrote:

> >  I used "RUNTESTFLAGS=--target-board native-gdbserver gdb.base/hbreak.exp"
> > exactly.
> >
> 
> --target-board != --target_board
>         ^                 ^
> 
> '-' vs '_'

 Good catch, thanks.  The result is:

                === gdb Summary ===

# of expected passes            43
# of unexpected failures        28

with the first failure being:

(gdb) Process [...]/build-i386/gdb/testsuite/gdb.base/break 
created; pid = 16195
Listening on port 2346
target remote localhost:2346
Remote debugging using localhost:2346
Remote debugging from host 127.0.0.1
0x40000c20 in ?? () from /lib/ld-linux.so.2
(gdb) continue
Continuing.
Couldn't write debug register: No such process.
(gdb) FAIL: gdb.base/hbreak.exp: run until function breakpoint

That message comes from i386_linux_dr_set(), so that looks like a bug 
somewhere with `gdbserver' not passing correct breakpoint data downstream.  
Which is obviously not a bug with the test script itself, but if people 
insist on keeping the bug I could make the script conditional on 
"gdb,no_hardware_watchpoints".

  Maciej