Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <palves@redhat.com>
To: Peter Bergner <bergner@vnet.ibm.com>, Alan Modra <amodra@gmail.com>
Cc: Ulrich Weigand <uweigand@de.ibm.com>,
	gdb-patches@sourceware.org,
	       binutils <binutils@sourceware.org>
Subject: Re: [PATCH, RFC] Add support for choosing disassembler cpu in GDB for POWER.
Date: Thu, 06 Oct 2016 09:52:00 -0000	[thread overview]
Message-ID: <ca0c9833-cf2f-1945-3c5c-94bba2c07718@redhat.com> (raw)
In-Reply-To: <5a66aca9-dfe9-7c44-21f9-27774a07d143@vnet.ibm.com>

How do you envision this command working if you consider
--enable-targets=all?  How would we make it work with other architectures?
Consider combined debuggers.  The fact that the default is explicitly
"power9" seems will make generalizing the command awkward?
If we made the default be "", and then had a per-arch default,
maybe it'd work?

But, I suspect that if need to explicitly set one disassembler cpu
when debugging a frame of $arch1, and explicitly set another disassembler
cpu when debugging a frame of $arch2, you'll end up with lots of
juggling.  And that juggling is only possible if you only consider
explicit disassembling.  Things like "set disassemble-next-line" makes
that impossible, since it's gdb that decides when to disassemble.

Maybe we should instead make the command be "set powerpc disassembler-cpu", or
generally, "set $arch disassembler-cpu".  We have "set arm disassembler"
already.
But if we could have a single generic command, that'd be of course better.
It's worth it to think about how it'd work at the user-interface level,
even if we don't make any other arch use it right away.

Thanks,
Pedro Alves


  parent reply	other threads:[~2016-10-06  9:52 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-30  2:14 Peter Bergner
2016-09-30 17:55 ` Ulrich Weigand
2016-10-03 20:25   ` Peter Bergner
2016-10-03 22:25     ` Alan Modra
2016-10-06  3:00       ` Peter Bergner
2016-10-06  4:44         ` Alan Modra
2016-10-06  9:52         ` Pedro Alves [this message]
2016-10-06 19:26           ` Peter Bergner
2016-10-07 19:21             ` Ulrich Weigand
2016-10-07 21:01               ` Peter Bergner
2016-10-08 14:39                 ` Ulrich Weigand
2016-10-10 23:28               ` Peter Bergner
2016-10-12  8:08                 ` Ulrich Weigand
2016-10-12 10:46                   ` Pedro Alves
2016-10-11  0:09             ` Pedro Alves
2016-10-11 18:49               ` Peter Bergner
2016-10-12  8:25                 ` Ulrich Weigand
2016-10-27  0:04                   ` Peter Bergner
2016-10-27  9:40                     ` Pedro Alves
2016-10-28 13:47                       ` Peter Bergner
2016-10-28 14:10                         ` Pedro Alves
2016-10-28 14:24                           ` Peter Bergner
2016-10-28 14:30                             ` Pedro Alves
2016-10-28 14:53                               ` Peter Bergner
2016-11-03 11:01                                 ` Pedro Alves
2016-11-03 15:02                                   ` Peter Bergner
2016-11-03 15:06                                     ` Peter Bergner
2016-11-03 16:41                                     ` Ulrich Weigand
2016-11-03 16:49                                       ` Peter Bergner
2016-10-28 12:32                     ` Ulrich Weigand
2016-10-28 13:45                       ` Peter Bergner
2016-10-28 14:15                         ` Ulrich Weigand
2016-10-28 15:02                           ` Peter Bergner
2016-10-28 18:47                             ` Ulrich Weigand
2016-11-02 23:28                               ` Peter Bergner
2016-10-12 19:35                 ` Pedro Alves

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=ca0c9833-cf2f-1945-3c5c-94bba2c07718@redhat.com \
    --to=palves@redhat.com \
    --cc=amodra@gmail.com \
    --cc=bergner@vnet.ibm.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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