From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: vladimir@codesourcery.com
Cc: gdb@sources.redhat.com
Subject: Re: gdb.base/watchpoint-solib.exp
Date: Sun, 13 Jul 2008 17:06:00 -0000 [thread overview]
Message-ID: <200807131704.m6DH4ugw014744@brahms.sibelius.xs4all.nl> (raw)
In-Reply-To: <g5dbl0$5t8$1@ger.gmane.org> (message from Vladimir Prus on Sun, 13 Jul 2008 20:48:39 +0400)
> From: Vladimir Prus <vladimir@codesourcery.com>
> Date: Sun, 13 Jul 2008 20:48:39 +0400
>
> Mark Kettenis wrote:
>
> > Hi Vladimir,
> >
> > The watchpoint-solib.exp test seems to assume hardware watchpoints:
> >
> > gdb_test "watch g" "Hardware watchpoint 3: g" "set watchpoint on g"
> >
> > Is this intentional, or should this be changed to accept "normal"
> > software watchpoints too?
>
> Hi Mark,
>
> this test was added by
> http://article.gmane.org/gmane.comp.gdb.patches/37556 and that
> commits changes the way the memory locations to watch are stored and
> handled for watchpoint. Since software watchpoints do not actually
> have any memory locations to watch, I suspect that the crash this
> test is supposed to guard against did not happen with software
> watchpoints.
Ah, if you want to explicity test hardware watchpoints, perhaps we
should test that the target supports them and skip the test otherwise.
> Are you on a target with no hardware breakpoints?
Yes I am. OpenBSD doesn't support hardware watchpoints on any of its
platforms. But even many Linux targets don't support hardware
watchpoints.
next prev parent reply other threads:[~2008-07-13 17:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-13 15:09 gdb.base/watchpoint-solib.exp Mark Kettenis
2008-07-13 16:49 ` gdb.base/watchpoint-solib.exp Vladimir Prus
2008-07-13 17:06 ` Mark Kettenis [this message]
2008-07-13 17:53 ` gdb.base/watchpoint-solib.exp Vladimir Prus
2008-07-13 18:21 ` gdb.base/watchpoint-solib.exp Daniel Jacobowitz
2008-07-16 2:48 ` gdb.base/watchpoint-solib.exp Michael Snyder
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=200807131704.m6DH4ugw014744@brahms.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb@sources.redhat.com \
--cc=vladimir@codesourcery.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