From: Nigel Stephens <nigel@mips.com>
To: Daniel Jacobowitz <dan@debian.org>
Cc: Carsten Langgaard <carstenl@mips.com>,
Ralf Baechle <ralf@linux-mips.org>,
linux-mips@linux-mips.org
Subject: Re: GDB patch
Date: Wed, 11 Dec 2002 17:24:44 +0000 [thread overview]
Message-ID: <3DF774DC.3010607@mips.com> (raw)
In-Reply-To: 20021211165218.GA11767@nevyn.them.org
Daniel Jacobowitz wrote:
>>Certainly 'p' is the logical inverse of 'P', so we'll change our gdb
>>remote stub to use that. So how about accepting Carsten's change, with
>>the 'R' case removed, and 'r' changed to 'p'?
>>
>>
>
>Can't do it. I strongly suspect that it will render the stub unusable
>with current versions of FSF GDB. Your tools add an explicit size to
>the packet and the community tools do not; so when they probe for and
>discover the P packet, they will probably try to use it and get
>confused. That's why I'd like to discuss this on the GDB list first.
>
>
I don't see why it wouldn't work:
1) Existing FSF gdb doesn't use 'p' yet anyway - it will continue to
work as before, using the 'g' request to fetch all the registers.
2) If and when gdb does use 'p', then there's still no problem - if the
kernel gdb stub sees a 'p' request without the ":SIZE" extension, it can
just treat it like the FSF protocol and use the "default" register size.
Nigel
next prev parent reply other threads:[~2002-12-11 17:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 19:19 GDB patch 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 [this message]
2002-12-11 17:56 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2002-12-10 12:07 Carsten Langgaard
2002-12-10 16:51 ` 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=3DF774DC.3010607@mips.com \
--to=nigel@mips.com \
--cc=carstenl@mips.com \
--cc=dan@debian.org \
--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