Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Richard Earnshaw <rearnsha@arm.com>
To: gdb@sources.redhat.com
Cc: Richard.Earnshaw@arm.com
Subject: Multi-arch and user-control of architecture flags
Date: Wed, 15 May 2002 02:32:00 -0000	[thread overview]
Message-ID: <200205150932.KAA23374@cam-mail2.cambridge.arm.com> (raw)


More random thoughts that I thought worth writing down before I forget 
them...

The current way to allow for a user to control some aspect of a target is 
to add a "set" command so that they can control a flag, for example, the 
ARM target has

  set apcs32 true/flase

to control whether the debugger should work with the processor in 26-bit 
mode or 32-bit mode.

As we move towards supporting multiple processors in a single GDB this is 
going to become increasingly confusing if we continue down this line, and 
it will become very unclear (to the poor user) which options apply to 
which target.

So how feasible would it be to extend the "set" and "show" commands so 
that they could sub-set the information?  For example, to allow

  set <target> <var> <value>

and 

  show <target> <var>

or even

  show <target>

to show all variables specific to the target.

If this isn't particularly practical, then perhaps we need a new command 
(tset/tshow?) that provides this.

R.


             reply	other threads:[~2002-05-15  9:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15  2:32 Richard Earnshaw [this message]
2002-05-15  3:23 ` Eli Zaretskii
2002-05-15  7:04   ` Andrew Cagney
2002-05-15  7:11     ` Richard Earnshaw
2002-05-15  7:21       ` Andrew Cagney
2002-05-16  6:49       ` Andrew Cagney
2002-05-16  6:59         ` Richard Earnshaw

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=200205150932.KAA23374@cam-mail2.cambridge.arm.com \
    --to=rearnsha@arm.com \
    --cc=Richard.Earnshaw@arm.com \
    --cc=gdb@sources.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