Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Andreas Arnez <arnez@linux.vnet.ibm.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] watchpoint-reuse-slot.exp: Correctly skip unsupported commands.
Date: Thu, 26 Jun 2014 14:15:00 -0000	[thread overview]
Message-ID: <53AC2AE6.7060401@redhat.com> (raw)
In-Reply-To: <87pphvhj6i.fsf@br87z6lw.de.ibm.com>

On 06/26/2014 02:52 PM, Andreas Arnez wrote:
> The test case "watchpoint-reuse-slot.exp" yields a lot of failures on
> s390/s390x: all instances of awatch, rwatch, and hbreak are performed
> even though they aren't supported on these targets.  This is because
> the test case ignores non-support error messages when probing for
> support of these commands, like:
> 
>     (gdb) rwatch buf.byte[0]
>     Target does not support this type of hardware watchpoint.
> 
> The patch adds handling for this case in the appropriate
> gdb_test_multiple invocations.

Thank you.

Looks like I only hacked out target_insert_watchpoint/hw_breakpoint
in my testing to return unsupported, which is what leads to the
"You may have requested too many" regexs in place:

 (top-gdb) awatch args.argc
 Hardware access (read/write) watchpoint 4: args.argc
 Warning:
 Could not insert hardware watchpoint 4.
 Could not insert hardware breakpoints:
 You may have requested too many hardware breakpoints/watchpoints.

We get that that error too when debugging against gdbserver with
Z packets disabled, which I also tested.

We get that alternative error if the target_can_use_hw_breakpoint
method returns false, which I forgot to hack/test.

> 
> gdb/testsuite/
> 	* gdb.base/watchpoint-reuse-slot.exp: Handle the case that the
> 	target lacks support for watch, awatch, rwatch, or hbreak.

s/watch, // , I think, as "watch" falls back to software
watchpoints.

Patch is OK.

Thanks!

-- 
Pedro Alves


  reply	other threads:[~2014-06-26 14:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-26 13:52 Andreas Arnez
2014-06-26 14:15 ` Pedro Alves [this message]
2014-06-26 15:21   ` Andreas Arnez
2014-06-30 11:36     ` Ulrich Weigand

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=53AC2AE6.7060401@redhat.com \
    --to=palves@redhat.com \
    --cc=arnez@linux.vnet.ibm.com \
    --cc=gdb-patches@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