From: "Eli Zaretskii" <eliz@gnu.org>
To: Paul Schlie <schlie@comcast.net>
Cc: drow@false.org, gdb@sourceware.org
Subject: Re: Available registers as a target property
Date: Sat, 07 May 2005 19:26:00 -0000 [thread overview]
Message-ID: <01c5533a$Blat.v2.4$5ad8e6a0@zahav.net.il> (raw)
In-Reply-To: <BEA18A5F.A129%schlie@comcast.net> (message from Paul Schlie on Fri, 06 May 2005 20:55:59 -0400)
> Date: Fri, 06 May 2005 20:55:59 -0400
> From: Paul Schlie <schlie@comcast.net>
> CC: <gdb@sourceware.org>
>
> it seems more consistent to enable GDB to select which of N register
> models to assume based upon the target's identification, than
> requiring the target to supply a detailed description of it's own
> register model; thereby not requiring any otherwise unnecessary
> complexity be added to the target's GDB server implementation?
I disagree: the target specifics should be localized to the target,
they should not invade the application-level GDB sources.
Apart of the purity of design issue, keeping target specifics in the
target code is also more practical: GDB maintenance tends to have
target experts responsible for the target-specific source files, while
the GDB higher-level parts are maintained by people who know less
about specific target features.
So I agree with Daniel: this knowledge should not be pushed into
higher GDB levels.
next prev parent reply other threads:[~2005-05-07 19:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-06 22:46 Paul Schlie
2005-05-06 23:27 ` Daniel Jacobowitz
2005-05-07 0:56 ` Paul Schlie
2005-05-07 1:36 ` Daniel Jacobowitz
2005-05-07 3:49 ` Paul Schlie
2005-05-07 4:30 ` Daniel Jacobowitz
2005-05-07 4:54 ` Paul Schlie
2005-05-07 5:41 ` Daniel Jacobowitz
2005-05-07 15:19 ` Paul Schlie
2005-05-07 19:26 ` Eli Zaretskii [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-06 17:55 Decker, Paul
2005-05-06 20:59 ` Daniel Jacobowitz
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='01c5533a$Blat.v2.4$5ad8e6a0@zahav.net.il' \
--to=eliz@gnu.org \
--cc=drow@false.org \
--cc=gdb@sourceware.org \
--cc=schlie@comcast.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).