From: Andrew Cagney <ac131313@cygnus.com>
To: Quality Quorum <qqi@world.std.com>
Cc: gdb@sourceware.cygnus.com
Subject: Re: remote nits
Date: Tue, 14 Dec 1999 15:02:00 -0000 [thread overview]
Message-ID: <3856CC46.6DAF9750@cygnus.com> (raw)
In-Reply-To: <Pine.SGI.3.95.991214105557.17037A-100000@world.std.com>
Quality Quorum wrote:
>
> On Wed, 15 Dec 1999, Andrew Cagney wrote:
>
> > Quality Quorum wrote:
> > >
> > >
> > > ???????? As far as I understand the document normal response to
> > > Rcmd is a sequence of zero of more 'O' packets followed, by OK or 'ENN'.
> >
> > One of the specified return codes is:
> >
> > reply OUTPUT
> > A command response with the hex encoded output string OUTPUT.
>
> This one should be outlawed before it is too late, it simply does not
> make any sense.
Sorry, to late. Technically it is the ``OOUTPUT'' bit that shouldn't be
there. Only the qRcmd packet supports it. However, I do see your
point.
Andrew
From toy@rtp.ericsson.se Tue Dec 14 15:29:00 1999
From: Raymond Toy <toy@rtp.ericsson.se>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb@sourceware.cygnus.com
Subject: Re: Sparc V9 disassembly?
Date: Tue, 14 Dec 1999 15:29:00 -0000
Message-id: <14422.53941.521702.962384@rtp.ericsson.se>
References: <14421.15563.476881.755513@rtp.ericsson.se> <3855DB8F.8EC29AB3@cygnus.com>
X-SW-Source: 1999-q4/msg00509.html
Content-length: 1009
>>>>> "Andrew" == Andrew Cagney <ac131313@cygnus.com> writes:
>>
>> info archi
>> set archi sparc:v9a
>> disassemble <addr1> <addr2>
>>
>> It seems the bug is in gdb_print_insn_sparc. It sets info->mach to
>> TM_PRINT_INSN_MACH, which is the sparc/sparclite. If I use gdb to
>> change this to 8 (sparc v9?), the disassembler recognizes the v9
>> instructions.
>>
>> Is this correct behavior?
Andrew> I'd try it with the current GDB however, I suspect that SPARC GDB
Andrew> currently ignores requests to change the architecture via ``set
Andrew> architecture''.
I commented out the offending line in gdb_print_insn_sparc, and
recompiled. Everything seems to work according to the way I want, so
set architecture does work. A peek at the code seems to indicate that
as well.
I will, however, try the most recent snapshot.
Since the code has made a conscious effort to set info->mach, I wasn't
really sure if everything else would work.
Ray
next parent reply other threads:[~1999-12-14 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SGI.3.95.991214105557.17037A-100000@world.std.com>
1999-12-14 15:02 ` Andrew Cagney [this message]
1999-12-14 15:31 ` Quality Quorum
[not found] <3855F0D8.12905961@cygnus.com>
1999-12-14 6:47 ` Quality Quorum
1999-12-14 7:35 ` Andrew Cagney
1999-12-15 5:53 ` Quality Quorum
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=3856CC46.6DAF9750@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sourceware.cygnus.com \
--cc=qqi@world.std.com \
/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