From: Daniel Jacobowitz <dan@debian.org>
To: Carsten Langgaard <carstenl@mips.com>
Cc: Ralf Baechle <ralf@linux-mips.org>, linux-mips@linux-mips.org
Subject: Re: GDB patch
Date: Tue, 10 Dec 2002 11:51:33 -0500 [thread overview]
Message-ID: <20021210165133.GA8818@nevyn.them.org> (raw)
In-Reply-To: <3DF5D902.22E5AA55@mips.com>
On Tue, Dec 10, 2002 at 01:07:31PM +0100, Carsten Langgaard wrote:
> I've attached a patch for gdb-stub.c to make it work better with the
> sde-gdb.
> These changes should be backwards compatible with a standard gdb, so it
> shouldn't break anything.
> Ralf, could you please apply it.
Strongly object. While I didn't check the implementation, it's nice to
see 'X' implemented. And P. But what the heck is this?
> @@ -816,13 +839,64 @@
> case 'k' :
> break; /* do nothing */
>
> + case 'R':
> + /* RNN[:SS], Set the value of CPU register NN (size SS) */
> + /* FALL THROUGH */
> - /*
> - * Reset the whole machine (FIXME: system dependent)
> - */
> case 'r':
> - break;
> + /* rNN[:SS] Return the value of CPU register NN (size SS) */
We're not making up a protocol here, we're implementing one. R and r
don't have anything to do with setting registers.
> + case 'D':
> + putpacket("OK");
> + return;
> + /* NOTREACHED */
>
> /*
> * Step to next instruction
'D' should generally resume the machine, by the way.
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2002-12-10 16:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 12:07 GDB patch Carsten Langgaard
2002-12-10 16:51 ` Daniel Jacobowitz [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-12-10 19:19 Nigel Stephens
2002-12-10 19:19 ` Nigel Stephens
2002-12-10 19:32 ` Daniel Jacobowitz
2002-12-10 20:40 ` Nigel Stephens
2002-12-11 16:52 ` Daniel Jacobowitz
2002-12-11 17:24 ` Nigel Stephens
2002-12-11 17:56 ` 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=20021210165133.GA8818@nevyn.them.org \
--to=dan@debian.org \
--cc=carstenl@mips.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.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