From: Joel Brobecker <brobecker@adacore.com>
To: uweigand@de.ibm.com, gdb-patches@sourceware.org
Subject: [RFA] Add comment describing the target_gdbarch global
Date: Thu, 07 May 2009 00:54:00 -0000 [thread overview]
Message-ID: <20090507005348.GA11074@adacore.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 530 bytes --]
Hello,
I remember a few months ago when I stumbled across a piece of code
using target_gdbarch, and I couldn't remember what this global was,
and what the different was with gdbarch. I eventually found the
original discussion again
(http://sourceware.org/ml/gdb-patches/2008-08/msg00358.html)
but I think a comment would be nice. I'm finally writing one today.
Does this look accurate?
2009-05-06 Joel Brobecker <brobecker@adacore.com>
* gdbarch.h (target_gdbarch): Add comment documenting this global.
--
Joel
[-- Attachment #2: comment.diff --]
[-- Type: text/x-diff, Size: 851 bytes --]
diff --git a/gdb/gdbarch.h b/gdb/gdbarch.h
index 5e508d7..31c935f 100644
--- a/gdb/gdbarch.h
+++ b/gdb/gdbarch.h
@@ -54,6 +54,17 @@ struct displaced_step_closure;
struct core_regset_section;
extern struct gdbarch *current_gdbarch;
+
+/* The architecture associated with the connection to the target.
+
+ The architecture vector provides some information that is really
+ a property of the target: The layout of certain packets, for instance;
+ or the solib_ops vector. Etc. To differentiate architecture accesses
+ to per-target properties to per-thread/pre-frame/per-objfile properties,
+ accesses to per-target properties should be made through target_gdbarch.
+
+ Eventually, when support for multiple targets is implemented in
+ GDB, this global should be made target-specific. */
extern struct gdbarch *target_gdbarch;
next reply other threads:[~2009-05-07 0:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-07 0:54 Joel Brobecker [this message]
2009-05-07 12:09 ` Ulrich Weigand
2009-05-07 14:53 ` Joel Brobecker
2009-05-14 14:00 ` Ulrich Weigand
2009-05-14 19:19 ` Joel Brobecker
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=20090507005348.GA11074@adacore.com \
--to=brobecker@adacore.com \
--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