From: Masaki Muranaka <monaka@monami-software.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Daniel Jacobowitz <drow@false.org>,
gdb-patches@sourceware.org, binutils@sourceware.org
Subject: Re: Can't set architecture to m32c on m32c-elf-gdb.
Date: Wed, 06 Jan 2010 23:24:00 -0000 [thread overview]
Message-ID: <271DFD02-74A7-4296-8253-AF4E24A38ADA@monami-software.com> (raw)
In-Reply-To: <4B44A991.4010101@redhat.com>
Hello Nick,
It might you feel you could set architecture to m32c,
BFD (bfd_default_scan) returns arch_info for m16c always.
This is the point.
Please try 'print $dma0' on GDB (w/o my patch).
(gdb) show architecture
The target architecture is set automatically (currently m16c)
(gdb) set architecture m32c
The target architecture is assumed to be m32c
(gdb) show architecture
The target architecture is assumed to be m32c
(gdb) print $dma0
$1 = void
dma0 is a register supported by m32c only.
So the result of 'print $dma0' is ...
In case m32c, it should be 'No registers.'
In case m16c, it should be ''void' since it doesn't have dma0 register.
Thanks,
On 2010/01/07, at 0:17, Nick Clifton wrote:
> Hi Masaki,
>
>> Really did you try them? Here is a log of my GDB.
>> (gdb) show architecture
>> The target architecture is set automatically (currently m16c)
>> (gdb) set architecture m32c:m32c
>> Undefined item: "m32c:m32c".
>> (gdb) set architecture m32c:m16c
>> Undefined item: "m32c:m16c".
>
> Point. But when I try this:
>
> (gdb) show architecture
> The target architecture is set automatically (currently m16c)
> (gdb) set architecture m32c
> The target architecture is assumed to be m32c
> (gdb) show architecture
> The target architecture is assumed to be m32c
> (gdb) set architecture m16c
> The target architecture is assumed to be m16c
> (gdb) show architecture
> The target architecture is assumed to be m16c
>
> So it appears that you can set the architecture to m32c, yes ?
>
> Cheers
> Nick
>
--
Masaki Muranaka
Monami software
next prev parent reply other threads:[~2010-01-06 23:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-03 9:17 Masaki Muranaka
2008-12-03 14:08 ` Daniel Jacobowitz
2008-12-04 1:04 ` Masaki Muranaka
2008-12-04 4:27 ` Daniel Jacobowitz
2008-12-04 6:48 ` Masaki Muranaka
2008-12-04 13:13 ` Daniel Jacobowitz
2008-12-04 14:22 ` Pedro Alves
2008-12-05 0:29 ` Masaki Muranaka
2009-12-28 2:32 ` Masaki Muranaka
2009-12-31 12:22 ` Nick Clifton
2010-01-03 0:00 ` Masaki Muranaka
2010-01-06 8:18 ` [patch] " Masaki Muranaka
2010-01-06 15:17 ` Nick Clifton
2010-01-06 23:24 ` Masaki Muranaka [this message]
2010-01-07 15:54 ` Nick Clifton
2010-01-07 22:38 ` Masaki Muranaka
2010-01-07 22:45 ` DJ Delorie
2010-01-08 0:02 ` Masaki Muranaka
2010-01-08 0:07 ` DJ Delorie
2010-01-08 0:45 ` Masaki Muranaka
2010-01-08 11:40 ` Nick Clifton
2010-01-12 0:04 ` Masaki Muranaka
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=271DFD02-74A7-4296-8253-AF4E24A38ADA@monami-software.com \
--to=monaka@monami-software.com \
--cc=binutils@sourceware.org \
--cc=drow@false.org \
--cc=gdb-patches@sourceware.org \
--cc=nickc@redhat.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