Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Pedro Alves <palves@redhat.com>
Cc: GDB Patches <gdb-patches@sourceware.org>,
	       Gabriel Krisman Bertazi <gabriel@krisman.be>
Subject: Re: [PATCH 3/3] Testcase
Date: Tue, 18 Nov 2014 20:20:00 -0000	[thread overview]
Message-ID: <87vbmcw9ai.fsf@redhat.com> (raw)
In-Reply-To: <546B6208.3030100@redhat.com>

On Tuesday, November 18 2014, Pedro Alves wrote:

> On 11/18/2014 03:30 AM, Sergio Durigan Junior wrote:
>> +    with_test_prefix "multiple targets" {
>
> s/multiple targets/multiple architectures/

Sorry, fixed.

> Otherwise looks good.  One question:
>
>> +	# We are not interested in loading any binary here,
>
> This is fine, though ...
>
>> and in
>> +	# some systems (PowerPC, for example), if we load a binary
>> +	# there is no way to set other architecture.
>
> ... eh.  I wasn't aware of that.  What does GDB say?

Here is what I see on a Fedora 20 PPC64 box:

  (gdb) set architecture 
  Requires an argument. Valid arguments are rs6000:6000, rs6000:rs1,
  rs6000:rsc, rs6000:rs2, powerpc:common64, powerpc:common, powerpc:603,
  powerpc:EC603e, powerpc:604, powerpc:403, powerpc:601, powerpc:620,
  powerpc:630, powerpc:a35, powerpc:rs64ii, powerpc:rs64iii, powerpc:7400,
  powerpc:e500, powerpc:e500mc, powerpc:e500mc64, powerpc:MPC8XX,
  powerpc:750, powerpc:titan, powerpc:vle, powerpc:e5500, powerpc:e6500,
  auto.
  (gdb) set architecture powerpc:common
  Architecture `powerpc:common' not recognized.
  The target architecture is set automatically (currently
  powerpc:common64)

-- 
Sergio
GPG key ID: 0x65FC5E36
Please send encrypted e-mail if possible
http://sergiodj.net/


  reply	other threads:[~2014-11-18 20:20 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13  0:18 [PATCH] Partial fix for PR breakpoints/10737: Make syscall info be per-arch instead of global Sergio Durigan Junior
2014-11-13  0:18 ` [PATCH 3/3] Testcase Sergio Durigan Junior
2014-11-14 15:54   ` Pedro Alves
2014-11-18  3:30     ` Sergio Durigan Junior
2014-11-18 15:13       ` Pedro Alves
2014-11-18 20:20         ` Sergio Durigan Junior [this message]
2014-11-19  9:23           ` PowerPC: "set architecture" -> "Architecture not recognized" ? (was: Re: [PATCH 3/3] Testcase) Pedro Alves
2014-11-19 18:46             ` PowerPC: "set architecture" -> "Architecture not recognized" ? Sergio Durigan Junior
2014-11-20 10:48               ` Pedro Alves
2014-11-20 17:20                 ` Sergio Durigan Junior
2014-11-13  0:18 ` [PATCH 2/3] Adjust calls for setting "catch syscall" information Sergio Durigan Junior
2014-11-14 15:53   ` Pedro Alves
2014-11-14 23:18     ` Sergio Durigan Junior
2014-11-13  0:18 ` [PATCH 1/3] Making syscall information be per-arch, instead of global Sergio Durigan Junior
2014-11-14 15:53   ` Pedro Alves
2014-11-14 23:17     ` Sergio Durigan Junior
2014-11-20 17:34 ` [PATCH] Partial fix for PR breakpoints/10737: Make syscall info be per-arch " Sergio Durigan Junior

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=87vbmcw9ai.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gabriel@krisman.be \
    --cc=gdb-patches@sourceware.org \
    --cc=palves@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