From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Yao Qi <yao@codesourcery.com>, Tom Tromey <tromey@redhat.com>,
"Philippe Waroquiers" <philippe.waroquiers@skynet.be>
Subject: Re: ping: Re: PATCH : allow to set length of hw watchpoints (e.g. for Valgrind gdbserver)
Date: Tue, 31 May 2011 17:31:00 -0000 [thread overview]
Message-ID: <201105311830.59328.pedro@codesourcery.com> (raw)
In-Reply-To: <4DE317B1.1040200@codesourcery.com>
On Monday 30 May 2011 05:06:09, Yao Qi wrote:
> > I can't say I understand why was that being proposed in this case?
> > What is the patch breaking?
> >
>
> One new command "set remote hardware-watchpoint-length-limit"
> is added in the patch, which is only useful to gdbserver+valgrind.
> When gdb is talking with normal gdbserver, it may be wrong to set
> hardware-watchpoint-length-limit in gdb side. Users should be careful
> when using this command.
If that was the only problem, than it'd be okay --- the user just
shouldn't use the command then. GDB will just do what the
user told it to. But, it looks like the patch changes the
behavior _even_ if the user doesn't use the command.
> The ideal solution, IMO, is remote side gives GDB the value of
> hardware-watchpoint-length-limit, however, I don't know it is easy or
> hard to do such thing.
We've also discussed completely getting rid of watchpoint
resources accounting recently.
--
Pedro Alves
next prev parent reply other threads:[~2011-05-31 17:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-21 22:20 Philippe Waroquiers
2011-05-26 19:02 ` Tom Tromey
2011-05-29 13:01 ` Philippe Waroquiers
2011-05-30 15:26 ` Joel Brobecker
2011-05-31 19:07 ` x86 watchpoints bug (Re: ping: Re: PATCH : allow to set length of hw watchpoints (e.g. for Valgrind gdbserver)) Pedro Alves
2011-05-31 20:25 ` Philippe Waroquiers
2011-05-31 20:53 ` Pedro Alves
2011-05-31 21:29 ` Pedro Alves
2011-05-31 22:15 ` Philippe Waroquiers
2011-05-31 23:04 ` Pedro Alves
2011-06-01 14:35 ` Pedro Alves
2011-06-08 22:55 ` Philippe Waroquiers
2011-06-09 0:00 ` Pedro Alves
2011-06-09 22:16 ` Philippe Waroquiers
2011-07-21 17:20 ` Pedro Alves
2011-07-22 16:40 ` Philippe Waroquiers
2011-07-22 16:43 ` Pedro Alves
2011-07-23 16:28 ` Thiago Jung Bauermann
2011-07-26 20:02 ` software watchpoints bug (was: Re: x86 watchpoints bug) Pedro Alves
2011-07-27 3:45 ` Thiago Jung Bauermann
2011-07-22 17:19 ` x86 watchpoints bug (Re: ping: Re: PATCH : allow to set length of hw watchpoints (e.g. for Valgrind gdbserver)) Pedro Alves
2011-05-27 3:25 ` ping: Re: PATCH : allow to set length of hw watchpoints (e.g. for Valgrind gdbserver) Yao Qi
2011-05-27 17:53 ` Tom Tromey
2011-05-27 17:59 ` Pedro Alves
2011-05-30 4:06 ` Yao Qi
2011-05-30 5:34 ` Philippe Waroquiers
2011-05-30 5:48 ` Yao Qi
2011-05-30 6:31 ` Philippe Waroquiers
2011-05-31 17:31 ` Pedro Alves [this message]
2011-05-31 18:06 ` Philippe Waroquiers
2011-06-01 15:15 ` Pedro Alves
2011-06-05 20:55 ` Philippe Waroquiers
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=201105311830.59328.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=philippe.waroquiers@skynet.be \
--cc=tromey@redhat.com \
--cc=yao@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