From: Daniel Jacobowitz <drow@false.org>
To: Michael Snyder <Michael.Snyder@palmsource.com>
Cc: Denis PILAT <denis.pilat@st.com>, gdb@sourceware.org
Subject: Re: gdbserver, was Re: remote validation
Date: Thu, 21 Sep 2006 20:56:00 -0000 [thread overview]
Message-ID: <20060921205558.GA4930@nevyn.them.org> (raw)
In-Reply-To: <1158871871.22863.5.camel@localhost.localdomain>
On Thu, Sep 21, 2006 at 01:51:11PM -0700, Michael Snyder wrote:
> 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?
Args can be made to work with the current gdbserver; the harness starts
a new process each time and we can pass things on the gdbserver command
line. Also, I have patches for another project which implement set
args directly over the remote protocol. I just haven't gotten round to
submitting that one yet.
The infrastructure for hardware watchpoints is in place. It just needs
more per-platform support, and some way to behave sensibly if the
target doesn't have any (the remote protocol behavior here is kind of
weak).
Inferior I/O is a heavy question. I don't know. I don't particularly
want to have gdbserver create slave ptys for this.
--
Daniel Jacobowitz
CodeSourcery
prev parent reply other threads:[~2006-09-21 20:56 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 ` gdbserver, was " Michael Snyder
2006-09-21 20:56 ` Daniel Jacobowitz [this message]
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=20060921205558.GA4930@nevyn.them.org \
--to=drow@false.org \
--cc=Michael.Snyder@palmsource.com \
--cc=denis.pilat@st.com \
--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