Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: James Ingham <jingham@cygnus.com>
To: Jim Blandy <jimb@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: RFA: handle sparse register sets in Insight register window
Date: Sat, 01 Apr 2000 00:00:00 -0000	[thread overview]
Message-ID: <14556.3528.975208.843365@leda.cygnus.com> (raw)
In-Reply-To: <200003242326.SAA17809@zwingli.cygnus.com>

Jim,

This looks okay, but in half the uses you only want the names of the
register, so wouldn't it be better to add a flag to gdb_regnames to
print out the index, so:

gdb_regnames

just prints out the names, and

gdb_regnames -index

prints out the list of pairs?

This would be simpler and faster on the Tcl end.  You can check for
the flag in gdb_regnames, and use the last argument of
map_arg_registers to pass in the value.

Jim




WARNING: multiple messages have this Message-ID

From: James Ingham <jingham@cygnus.com>
To: Jim Blandy <jimb@cygnus.com>
Cc: gdb-patches@sourceware.cygnus.com
Subject: Re: RFA: handle sparse register sets in Insight register window
Date: Fri, 24 Mar 2000 16:49:00 -0000	[thread overview]
Message-ID: <14556.3528.975208.843365@leda.cygnus.com> (raw)
Message-ID: <20000324164900.KkeONHcefr6K8nv0ZGpYqLXb7rZd73eU1cJZMuTXJxA@z> (raw)
In-Reply-To: <200003242326.SAA17809@zwingli.cygnus.com>

Jim,

This looks okay, but in half the uses you only want the names of the
register, so wouldn't it be better to add a flag to gdb_regnames to
print out the index, so:

gdb_regnames

just prints out the names, and

gdb_regnames -index

prints out the list of pairs?

This would be simpler and faster on the Tcl end.  You can check for
the flag in gdb_regnames, and use the last argument of
map_arg_registers to pass in the value.

Jim




       reply	other threads:[~2000-04-01  0:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200003242326.SAA17809@zwingli.cygnus.com>
2000-04-01  0:00 ` James Ingham [this message]
2000-03-24 16:49   ` James Ingham

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=14556.3528.975208.843365@leda.cygnus.com \
    --to=jingham@cygnus.com \
    --cc=gdb-patches@sourceware.cygnus.com \
    --cc=jimb@cygnus.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