From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: [obv] testsuite: read1 fix: gdb.arch/i386-dr3-watch.exp
Date: Mon, 15 Aug 2011 08:42:00 -0000 [thread overview]
Message-ID: <201108150941.43467.pedro@codesourcery.com> (raw)
In-Reply-To: <20110815075703.GA29081@host1.jankratochvil.net>
Whoops. Thanks Jan.
--
Pedro Alves
On Monday 15 August 2011 08:57:03, Jan Kratochvil wrote:
> Hi Pedro,
>
> with "read1" runtest
> [Bug testsuite/12649] New: reproducer for races of expect incomplete reads
> http://sourceware.org/bugzilla/show_bug.cgi?id=12649
> and therefore occasionally even during normal runs it will:
> FAIL: gdb.arch/i386-dr3-watch.exp: watch i1 still fits (got interactive prompt)
> FAIL: gdb.arch/i386-dr3-watch.exp: watch i2 still fits
> FAIL: gdb.arch/i386-dr3-watch.exp: watch i3 still fits
> FAIL: gdb.arch/i386-dr3-watch.exp: watch i4 still fits
> due to
> watch gap1
> Hardware watchpoint 7: gap1
> Warning:
> Could not insert hardware watchpoint 7.
> Could not insert hardware breakpoints:
> You may have requested too manyPASS: gdb.arch/i386-dr3-watch.exp: watchpoint on gap1 does not fit debug registers
> hardware breakpoints/watchpoints.
>
> (gdb) PASS: gdb.arch/i386-dr3-watch.exp: delete all watchpoints
> delete
> Delete all breakpoints? (y or n) watch i1
> Please answer y or n.
> Delete all breakpoints? (y or n) n
> (gdb) FAIL: gdb.arch/i386-dr3-watch.exp: watch i1 still fits (got interactive prompt)
>
> Checked in. Tested on {x86_64,x86_64-m32}-fedora16pre-linux-gnu.
>
>
> Thanks,
> Jan
>
>
> http://sourceware.org/ml/gdb-cvs/2011-08/msg00077.html
>
> --- src/gdb/testsuite/ChangeLog 2011/08/14 15:58:39 1.2834
> +++ src/gdb/testsuite/ChangeLog 2011/08/15 07:56:20 1.2835
> @@ -1,3 +1,9 @@
> +2011-08-15 Jan Kratochvil <jan.kratochvil@redhat.com>
> +
> + * gdb.arch/i386-dr3-watch.exp
> + (watchpoint on gap1 does not fit debug registers)
> + (delete all watchpoints): Fix racy expect strings.
> +
> 2011-08-14 Yao Qi <yao@codesourcery.com>
>
> * gdb.base/maint.exp: set data_section to ".neardata".
> --- src/gdb/testsuite/gdb.arch/i386-dr3-watch.exp 2011/07/22 16:58:32 1.2
> +++ src/gdb/testsuite/gdb.arch/i386-dr3-watch.exp 2011/08/15 07:56:20 1.3
> @@ -64,7 +64,7 @@
> # 4 if all were available).
> set test "watchpoint on gap1 does not fit debug registers"
> gdb_test_multiple "watch gap1" "$test" {
> - -re "Hardware watchpoint .*: gap1.*Warning:.*Could not insert hardware watchpoint.*You may have requested too many.*" {
> + -re "Hardware watchpoint .*: gap1.*Warning:.*Could not insert hardware watchpoint.*You may have requested too many.*\r\n$gdb_prompt $" {
> pass $test
> }
> -re "Hardware watchpoint .*: gap1\r\n$gdb_prompt $" {
> @@ -81,7 +81,7 @@
> gdb_test "delete" \
> "" \
> "delete all watchpoints" \
> - "Delete all breakpoints.*$" \
> + {Delete all breakpoints\? \(y or n\) $} \
> "y"
>
> # If debug registers were left occupied by mistake, we'll fail to set
>
prev parent reply other threads:[~2011-08-15 8:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 7:57 Jan Kratochvil
2011-08-15 8:42 ` Pedro Alves [this message]
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=201108150941.43467.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.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