From: Doug Evans <dje@google.com>
To: gdb-patches@sourceware.org
Subject: [RFA, RFA 7.6] Improve help for, e.g., running gdb in build tree.
Date: Wed, 27 Mar 2013 20:17:00 -0000 [thread overview]
Message-ID: <yjt2620c6675.fsf@ruffy2.mtv.corp.google.com> (raw)
Hi.
How about this for 7.6?
2013-03-27 Doug Evans <dje@google.com>
* python/python.c (finish_python_initialization): Provide suggestion
for how to tell gdb to find its python files.
Index: python.c
===================================================================
RCS file: /cvs/src/src/gdb/python/python.c,v
retrieving revision 1.111
diff -u -p -r1.111 python.c
--- python.c 12 Mar 2013 17:39:45 -0000 1.111
+++ python.c 27 Mar 2013 18:34:24 -0000
@@ -1714,6 +1714,7 @@ finish_python_initialization (void)
warning (_("Could not load the Python gdb module from `%s'."),
gdb_pythondir);
warning (_("Limited Python support is available from the _gdb module."));
+ warning (_("Suggest passing --data-directory=/path/to/gdb/data-directory."));
do_cleanups (cleanup);
return;
}
next reply other threads:[~2013-03-27 18:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-27 20:17 Doug Evans [this message]
2013-03-27 20:17 ` Tom Tromey
2013-03-27 20:44 ` Doug Evans
2013-03-28 12:00 ` Joel Brobecker
2013-03-28 19:46 ` Doug Evans
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=yjt2620c6675.fsf@ruffy2.mtv.corp.google.com \
--to=dje@google.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