From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: [RFA/Doco] Document new <data-dir>/system-gdbinit area
Date: Tue, 21 May 2013 09:25:00 -0000 [thread overview]
Message-ID: <1369128288-3495-1-git-send-email-brobecker@adacore.com> (raw)
This documents the introduction of new scripts provided in
a GDB install.
Ref: http://www.sourceware.org/ml/gdb-patches/2013-05/msg00382.html
gdb/doc/ChangeLog:
* gdb.texinfo (System-wide configuration): Add subsection
describing the scripts now available under the data-dir's
system-gdbbinit subdirectory.
OK to apply? Should I also add a NEWS entry for this?
Thank you,
--
Joel
---
gdb/doc/gdb.texinfo | 26 ++++++++++++++++++++++++++
1 file changed, 26 insertions(+)
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 43b0104..111e352 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -36332,6 +36332,32 @@ initialization. If the data-directory is changed after @value{GDBN} has
started with the @code{set data-directory} command, the file will not be
reread.
+@subsection System-wide configuration scripts provided by @value{GDBN}
+
+The @file{system-gdbinit} directory, located inside the data-directory
+(as specified by @option{--with-gdb-datadir} at configure time) contains
+a number of scripts which can be used as system-wide init files. To
+automatically source those scripts at startup, @value{GDBN} should be
+configured with @option{-with-system-gdbinit}. Otherwise, any user
+should be able to source them by hand as needed.
+
+The following scripts are currently available:
+@itemize @bullet
+
+@item @file{elinos.py}
+This script is useful when debugging a program on an ELinOS target.
+It takes advantage of the environment variables defined in a standard
+ELinOS environment in order to determine the location of the system
+shared libraries, and then sets the @samp{solib-absolute-prefix}
+and @samp{solib-search-path} variables appropriately.
+
+@item @file{wrs-linux.py}
+This script is useful when debugging a program on a target running
+Wind River Linux. It expects the @env{ENV_PREFIX} to be set to
+the host-side sysroot used by the target system.
+
+@end itemize
+
@node Maintenance Commands
@appendix Maintenance Commands
@cindex maintenance commands
--
1.7.10.4
next reply other threads:[~2013-05-21 9:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 9:25 Joel Brobecker [this message]
2013-05-21 15:34 ` Pedro Alves
2013-05-21 17:37 ` Eli Zaretskii
2013-05-21 17:17 ` Eli Zaretskii
2013-05-22 6:28 ` Joel Brobecker
2013-05-22 14:54 ` Eli Zaretskii
2013-05-23 6:08 ` Checked in: " Joel Brobecker
2013-05-24 1:33 ` asmwarrior
2013-05-24 4:53 ` Joel Brobecker
2013-05-24 5:06 ` Joel Brobecker
2013-05-24 6:24 ` Eli Zaretskii
2013-05-22 6:44 ` 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=1369128288-3495-1-git-send-email-brobecker@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
/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