From: Eli Zaretskii <eliz@elta.co.il>
To: Stephane Carrez <stcarrez@nerim.fr>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA]: Document tui reg commands
Date: Sun, 28 Mar 2004 13:40:00 -0000 [thread overview]
Message-ID: <ud66x84zz.fsf@elta.co.il> (raw)
In-Reply-To: <4066C5D4.5010109@nerim.fr> (message from Stephane Carrez on Sun, 28 Mar 2004 14:32:20 +0200)
>
> I agree. The semantics of 'system' is unclear to me. For 'save/restore'
> may be the TUI should skip them silently as they are related to gdb internals
> (registers that are saved/restored by gdb when it calls inferior functions).
>
> From my point of view, if these groups should ever be documented, they should
> be documented outside of the TUI chapter (but today this is the only place
> 'register group' is mentionned...; apart from mainainters commands...)
Agreed.
Can someone please donate a description of these register groups?
prev parent reply other threads:[~2004-03-28 13:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-19 0:09 Stephane Carrez
2004-03-13 14:21 ` Stephane Carrez
2004-03-19 0:09 ` Eli Zaretskii
2004-03-13 16:23 ` Eli Zaretskii
2004-03-28 12:32 ` Stephane Carrez
2004-03-28 13:40 ` Eli Zaretskii [this message]
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=ud66x84zz.fsf@elta.co.il \
--to=eliz@elta.co.il \
--cc=eliz@gnu.org \
--cc=gdb-patches@sources.redhat.com \
--cc=stcarrez@nerim.fr \
/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