From: Pierre Muller <muller@ics.u-strasbg.fr>
To: Daniel Jacobowitz <drow@mvista.com>, Andreas Schwab <schwab@suse.de>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC] Correct gdbserver register packets
Date: Tue, 03 Dec 2002 00:31:00 -0000 [thread overview]
Message-ID: <5.0.2.1.2.20021203092802.034b2c20@ics.u-strasbg.fr> (raw)
In-Reply-To: <20021203052113.GA22563@nevyn.them.org>
At 06:21 03/12/2002, Daniel Jacobowitz wrote:
>On Mon, Dec 02, 2002 at 11:44:31AM +0100, Andreas Schwab wrote:
>> Daniel Jacobowitz <drow@mvista.com> writes:
>>
>> |> Or else Andreas's patch to decrease the number of registers. Hmm,
>> |> probably doing it Andreas's way is better. I'll take care of this in
>> |> the morning.
>>
>> My way of fixing it is not complete, I get "Wrong sized register packet"
>> messages from gdbserver.
>
>There's a much easier solution: change the 31 to 29, and remove the
>extra two registers from regformats/. I'm not familiar with any m68k
>stubs; do you know of any others that do or do not include the extra
>two registers, which GDB no longer seems to know anything about? Or
>are they just bogus?
config/m68k/tm-sun3.h
seems to use 31 registers including the two not known by
other m68k targets...
But I don't known the state of that target...
next prev parent reply other threads:[~2002-12-03 8:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-26 9:29 Pierre Muller
2002-12-01 17:14 ` Daniel Jacobowitz
2002-12-02 2:44 ` Andreas Schwab
2002-12-02 6:14 ` Daniel Jacobowitz
2002-12-02 6:22 ` Pierre Muller
2002-12-02 6:57 ` Daniel Jacobowitz
2002-12-02 21:20 ` Daniel Jacobowitz
2002-12-03 0:31 ` Pierre Muller [this message]
2002-12-03 19:55 ` Daniel Jacobowitz
2002-12-04 4:28 ` Andreas Schwab
2003-01-04 21: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=5.0.2.1.2.20021203092802.034b2c20@ics.u-strasbg.fr \
--to=muller@ics.u-strasbg.fr \
--cc=drow@mvista.com \
--cc=gdb-patches@sources.redhat.com \
--cc=schwab@suse.de \
/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