Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@codesourcery.com>
To: Emi SUZUKI <emi-suzuki@tjsys.co.jp>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC] checking the Z-packet suppport on gdbserver
Date: Thu, 13 Sep 2007 17:05:00 -0000	[thread overview]
Message-ID: <m3sl5ixzpt.fsf@codesourcery.com> (raw)
In-Reply-To: <20070913.210822.19763360.emi-suzuki@tjsys.co.jp> (Emi SUZUKI's message of "Thu, 13 Sep 2007 21:08:22 +0900")


Emi SUZUKI <emi-suzuki@tjsys.co.jp> writes:
> GDB decides which type of watchpoints should be set when giving the
> command like "watch foo".  And hardware watchpoints can be used when
> gdbserver has the Z-packet support.  However, as the session log above
> has shown, GDB does not check the Z-packet support on gdbserver when
> deciding the type of the watchpoint but when actually setting the
> watchpoint to the target.  

Yeah, this is pretty losing behavior on GDB's part.

> Would anyone give me any comments how it should be treated as a whole?
> Defines another packet for it?  Applies as proposed and notes "it
> might not work with older versions of gdbserver" ?

I wonder, would it make sense to have GDB assume that hardware
watchpoints are *not* available on remote targets, and then have
gdbserver send a 'qSupported' packet stubfeature that tells GDB that
hardware watchpoints are okay?


  reply	other threads:[~2007-09-13 17:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-13 12:09 Emi SUZUKI
2007-09-13 17:05 ` Jim Blandy [this message]
2007-09-14  9:40   ` [RFC] checking the Z-packet support " Emi SUZUKI
2007-09-14 12:15     ` Daniel Jacobowitz
2007-09-18 21:17     ` Jim Blandy
2007-09-18 21:28       ` Daniel Jacobowitz
2007-09-18 21:45     ` Jim Blandy
2007-09-20  9:49       ` Emi SUZUKI
2007-09-14 12:15 ` [RFC] checking the Z-packet suppport " Daniel Jacobowitz

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=m3sl5ixzpt.fsf@codesourcery.com \
    --to=jimb@codesourcery.com \
    --cc=emi-suzuki@tjsys.co.jp \
    --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