From: Daniel Jacobowitz <drow@false.org>
To: Emi SUZUKI <emi-suzuki@tjsys.co.jp>
Cc: jimb@codesourcery.com, gdb-patches@sourceware.org
Subject: Re: [RFC] checking the Z-packet support on gdbserver
Date: Fri, 14 Sep 2007 12:15:00 -0000 [thread overview]
Message-ID: <20070914121550.GB18934@caradoc.them.org> (raw)
In-Reply-To: <20070914.183913.226021396.emi-suzuki@tjsys.co.jp>
On Fri, Sep 14, 2007 at 06:39:13PM +0900, Emi SUZUKI wrote:
> Meanwhile, I've found the definition below in gdb/config/nm-i386.h.
>
> #define TARGET_CAN_USE_HARDWARE_WATCHPOINT(type, cnt, ot) 1
>
> TARGET_CAN_USE_HARDWARE_WATCHPOINT is used in watch_command_1 for
> checking if the support of hardware watchpoints are available on the
> target. If it is not defined, the target vector function
> 'to_can_use_hw_breakpoint' would be called. So, the above implies
> that GDB built for the x86 native target is not supposed to debug the
> remote target. But it should be, to debug a target running on a
> remote machine which is the same architecture to the local host,
> shouldn't it?
> (Although it would not be much necessary in practice...)
Yes, this is a bug. It's a little tricky to fix because there's a
variety of different i386 targets sharing that header file, but it's
certainly fixable.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-09-14 12:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-13 12:09 [RFC] checking the Z-packet suppport " Emi SUZUKI
2007-09-13 17:05 ` Jim Blandy
2007-09-14 9:40 ` [RFC] checking the Z-packet support " Emi SUZUKI
2007-09-14 12:15 ` Daniel Jacobowitz [this message]
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=20070914121550.GB18934@caradoc.them.org \
--to=drow@false.org \
--cc=emi-suzuki@tjsys.co.jp \
--cc=gdb-patches@sourceware.org \
--cc=jimb@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