From: Andrew Cagney <ac131313@redhat.com>
To: Grant Edwards <grante@visi.com>
Cc: Raja Saleru <iap_sraja@access.co.jp>, Gdb <gdb@sources.redhat.com>
Subject: Re: GDB Server - remote serial protocol
Date: Wed, 04 Jun 2003 15:48:00 -0000 [thread overview]
Message-ID: <3EDE14AB.8050803@redhat.com> (raw)
In-Reply-To: <20030604091904.A26714@visi.com>
> On Tue, Jun 04, 2002 at 11:34:29AM +0900, Raja Saleru wrote:
>
> Dude, fix the date on your system. It's 2003. At least in
> this part of the world....
>
>
>> while remote debugging the application using gdb and gdbserver,
>> the user at host side can use the remote protocol commands only
>> ? or standard gdb commands ? or both ?
>
>
> The user uses standard gdb commands. The remote protocol is
> strictly an internal thing that the two gdbs use to talk to
> each other.
BTW, it's possible to send the remote end arbitrary requests using:
(gdb) monitor ....
The effect, and even the level of support, is entirely dependant on the
remote stub. Mutter something about security.
Andrew
prev parent reply other threads:[~2003-06-04 15:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-04 2:34 Raja Saleru
2003-06-04 14:24 ` Grant Edwards
2003-06-04 15:48 ` Andrew Cagney [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=3EDE14AB.8050803@redhat.com \
--to=ac131313@redhat.com \
--cc=gdb@sources.redhat.com \
--cc=grante@visi.com \
--cc=iap_sraja@access.co.jp \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).