Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Masaki Muranaka <monaka@monami-software.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org,  Daniel Jacobowitz <drow@false.org>,
	 binutils@sourceware.org
Subject: Re: Can't set architecture to m32c on m32c-elf-gdb.
Date: Fri, 05 Dec 2008 00:29:00 -0000	[thread overview]
Message-ID: <9646DD31-9D56-4139-B593-B5D30496F095@monami-software.com> (raw)
In-Reply-To: <200812041422.32953.pedro@codesourcery.com>

Hello,

The result of <tab><tab> is :

| This GDB was configured as "--host=i386-apple-darwin9.5.0 --target=m32c-elf".
| For bug reporting instructions, please see:
| <http://www.gnu.org/software/gdb/bugs/>.
| (gdb) set architecture 
| auto  m16c  m32c  


On 2008/12/04, at 23:22, Pedro Alves wrote:

> On Thursday 04 December 2008 13:12:24, Daniel Jacobowitz wrote:
>> On Thu, Dec 04, 2008 at 03:47:05PM +0900, Masaki Muranaka wrote:
>>>> See bfd_default_scan for more.  I guess it's because the architecture
>>>> is named "m32c", but the default flag is set for m16c.  If that's so,
>>>> "set architecture m32c:m32c" should work - does it?
>>>
>>> | For bug reporting instructions, please see:
>>> | <http://www.gnu.org/software/gdb/bugs/>.
>>> | (gdb) set architecture m32c:m32c
>>> | Undefined item: "m32c:m32c".
>>> | (gdb) set architecture m32c:m16c
>>> | Undefined item: "m32c:m16c".
>>>
>>> Should I put any commands before 'set architecture'?
>>
>> Strange.  I guess I don't understand how this works, then.  I thought
>> this would do it:
>>
>>  /* Given that printable_name contains no colon, attempt to match:
>>     ARCH_NAME [ ":" ] PRINTABLE_NAME?  */
>>
>
> The "Undefined item:" error comes from the fact that "set architecture" is
> an "enum" command, and gdb is complaining that those entries aren't listed
> as possible enumerations.
>
> All settings gdb will accept are shown with 'set architecture <tab><tab>'.
> What options does that show?
>
> -- 
> Pedro Alves
>

Masaki Muranaka
Monami Software





  reply	other threads:[~2008-12-05  0:29 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 [this message]
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
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=9646DD31-9D56-4139-B593-B5D30496F095@monami-software.com \
    --to=monaka@monami-software.com \
    --cc=binutils@sourceware.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=pedro@codesourcery.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