diff options
author | Joel Brobecker <brobecker@adacore.com> | 2014-03-07 09:00:27 -0800 |
---|---|---|
committer | Joel Brobecker <brobecker@adacore.com> | 2014-03-07 16:26:35 -0800 |
commit | 3156469ca870821d972a3f9d242379b86e622c95 (patch) | |
tree | 4c7ea713ee70a343e275c1d4bfb5ab43d23df30d /gdb/target.h | |
parent | 2ba229e2c9dd9bf25ed1a3647d789f367b24cff4 (diff) | |
download | gdb-3156469ca870821d972a3f9d242379b86e622c95.zip gdb-3156469ca870821d972a3f9d242379b86e622c95.tar.gz gdb-3156469ca870821d972a3f9d242379b86e622c95.tar.bz2 |
target.h: Expands complete_target_initialization and add_target comments.
Expand a bit the comments to answer some questions I had when looking
at why a target of mine would not have some default methods set.
gdb/ChangeLog:
* target.h (complete_target_initialization, add_target):
Add comment.
Diffstat (limited to 'gdb/target.h')
-rw-r--r-- | gdb/target.h | 6 |
1 files changed, 5 insertions, 1 deletions
diff --git a/gdb/target.h b/gdb/target.h index 91f0cc9..db9f5c3 100644 --- a/gdb/target.h +++ b/gdb/target.h @@ -2006,9 +2006,13 @@ int target_verify_memory (const gdb_byte *data, /* Routines for maintenance of the target structures... complete_target_initialization: Finalize a target_ops by filling in - any fields needed by the target implementation. + any fields needed by the target implementation. Unnecessary for + targets which are registered via add_target, as this part gets + taken care of then. add_target: Add a target to the list of all possible targets. + This only makes sense for targets that should be activated using + the "target TARGET_NAME ..." command. push_target: Make this target the top of the stack of currently used targets, within its particular stratum of the stack. Result |