From: Khoo Yit Phang <khooyp@cs.umd.edu>
To: GDB Patches <gdb-patches@sourceware.org>
Cc: Khoo Yit Phang <khooyp@cs.umd.edu>
Subject: [PATCH] Warn about data-directory when failing to import Python "gdb" module
Date: Mon, 17 Sep 2012 19:36:00 -0000 [thread overview]
Message-ID: <AF3745C0-8A7B-4D72-AF57-6F8F68A27357@cs.umd.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 295 bytes --]
Hi,
I'd like to add a warning when failing to import the Python "gdb" module to check that data-directory is set correctly, to address the confusion arising from the incompatibility between the old "gdb" module and the one I recently checked in.
Thank you,
Yit
September 17, 2012
[-- Attachment #2: warn-gdb-python-compat.txt --]
[-- Type: text/plain, Size: 681 bytes --]
gdb/ChangeLog
2012-09-17 Khoo Yit Phang <khooyp@cs.umd.edu>
* gdb/python.c (finish_python_initialization): Augment the warning
when importing "gdb" fails, to check that data-directory is set
correctly.
diff --git a/gdb/python/python.c b/gdb/python/python.c
--- a/gdb/python/python.c
+++ b/gdb/python/python.c
@@ -1484,6 +1484,7 @@
gdbpy_print_stack ();
warning (_("Could not load the Python gdb module from `%s'."),
gdb_pythondir);
+ warning (_("Please make sure that data-directory is set correctly."));
warning (_("Limited Python support is available from the _gdb module."));
do_cleanups (cleanup);
return;
next reply other threads:[~2012-09-17 19:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 19:36 Khoo Yit Phang [this message]
2012-09-17 20:23 ` Jan Kratochvil
2012-09-17 20:28 ` Khoo Yit Phang
2012-09-17 20:36 ` Jan Kratochvil
2012-09-17 20:58 ` Joel Brobecker
2012-09-17 21:04 ` Khoo Yit Phang
2012-09-18 20:40 ` Khoo Yit Phang
2012-09-22 13:30 ` Jan Kratochvil
2012-09-22 18:37 ` Khoo Yit Phang
2012-10-06 20:56 ` Ping! " Khoo Yit Phang
2012-09-18 6:17 ` Eli Zaretskii
2012-09-18 11:58 ` Jan Kratochvil
2012-09-18 12:21 ` Eli Zaretskii
2012-09-18 13:54 ` Joel Brobecker
2012-09-18 15:38 ` Khoo Yit Phang
2012-09-18 15:44 ` Jan Kratochvil
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=AF3745C0-8A7B-4D72-AF57-6F8F68A27357@cs.umd.edu \
--to=khooyp@cs.umd.edu \
--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