Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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: Sun, 03 Jan 2010 00:00:00 -0000	[thread overview]
Message-ID: <21F11493-3DE3-41FA-97D5-B539B54259A2@monami-software.com> (raw)
In-Reply-To: <4B3C9784.1040309@redhat.com>

Hello Nick,

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".

I got their sources via official git repository.

Thanks,

On 2009/12/31, at 21:22, Nick Clifton wrote:

> Hi Masaki,
> 
>> I figured out the reason about this issue.
>> This is caused by a bug in bfd/cpu-m32c.c.
>> The condision is like this:
>> He expects to select arch_info_struct[0] when he puts "set architecture m32c".
>> But bfd_m32c_arch is selected bfd_default_scan(). So he always gets
>> configuration for m16c instead of m32c.
> 
> But as Daniel pointed out, if the user enters the command:
> 
>  set architecture m32c:m32c
> 
> then the code in bfd_default_scan() will select the m32c architecture and if the user enters:
> 
>  set architecture m32c:m16c
> 
> then bfd_default_scan() will select the m16c architecture.
> 
>> I think printable names in bfd/cpu-m32.c should be changed to "m32c:m16c", "m32c:m32c".
> 
> There is no need for this, and in fact it will stop bfd_default_scan from working as intended.
> 
> Cheers
>  Nick
> 


  reply	other threads:[~2010-01-03  0:00 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 [this message]
2010-01-06  8:18         ` [patch] " Masaki Muranaka
2010-01-06 15:17         ` Nick Clifton
2010-01-06 23:24           ` Masaki Muranaka
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=21F11493-3DE3-41FA-97D5-B539B54259A2@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