From: Michael Snyder <Michael.Snyder@palmsource.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: Denis PILAT <denis.pilat@st.com>, gdb@sourceware.org
Subject: gdbserver, was Re: remote validation
Date: Thu, 21 Sep 2006 20:51:00 -0000 [thread overview]
Message-ID: <1158871871.22863.5.camel@localhost.localdomain> (raw)
In-Reply-To: <20060921143325.GA24126@nevyn.them.org>
On Thu, 2006-09-21 at 10:33 -0400, Daniel Jacobowitz wrote:
> # There's no support for argument-passing (yet).
> set_board_info noargs 1
>
> # Can't do input (or output) in the current gdbserver.
> set_board_info gdb,noinferiorio 1
>
> # Can't do hardware watchpoints, in general
> set_board_info gdb,no_hardware_watchpoints 1;
Not to highjack the thread, but... I'm wondering how much
interest / motivation there would be, to get a few of these
things (such as infiorior i/o) working in linux/gdbserver?
next prev parent reply other threads:[~2006-09-21 20:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 14:28 Denis PILAT
2006-09-21 14:33 ` Daniel Jacobowitz
2006-09-21 20:51 ` Michael Snyder [this message]
2006-09-21 20:56 ` gdbserver, was " 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=1158871871.22863.5.camel@localhost.localdomain \
--to=michael.snyder@palmsource.com \
--cc=denis.pilat@st.com \
--cc=drow@false.org \
--cc=gdb@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