From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Khoo Yit Phang <khooyp@cs.umd.edu>
Cc: Tom Tromey <tromey@redhat.com>, GDB Patches <gdb-patches@sourceware.org>
Subject: Re: Regression for --batch [Re: [RFC] Make python/lib/gdb and submodules proper Python modules]
Date: Fri, 14 Sep 2012 06:16:00 -0000 [thread overview]
Message-ID: <20120914061549.GA6011@host2.jankratochvil.net> (raw)
In-Reply-To: <B8F45A56-D29A-438F-9B15-1CF6BAD14B95@cs.umd.edu>
On Fri, 14 Sep 2012 07:59:46 +0200, Khoo Yit Phang wrote:
> Is ./gdb from a GDB build directory? If so, the error is expected; you'd
> need to run with -data-directory build-directory/gdb/data-directory, since
> much of the Python initialization has been moved into
> data-directory/python/gdb/__init__.py, and the old __init__.py is
> incompatible.
In such case there is a need to update gdb/contrib/cc-with-tweaks.sh .
runtest CC_FOR_TARGET=/bin/sh\ $PWD/../contrib/cc-with-tweaks.sh\ -i\ gcc gdb.base/display.exp
[...]
Running ./gdb.base/display.exp ...
gdb compile failed, Python Exception <type 'exceptions.NameError'> name 'os' is not defined:
warning: Could not load the Python gdb module from `/usr/share/gdb/python'.
warning: Limited Python support is available from the _gdb module.
=== gdb Summary ===
# of untested testcases 1
Regards,
Jan
next prev parent reply other threads:[~2012-09-14 6:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-03 3:44 [RFC] Make python/lib/gdb and submodules proper Python modules Khoo Yit Phang
2012-09-07 6:19 ` Doug Evans
2012-09-07 14:27 ` Khoo Yit Phang
2012-09-10 20:38 ` Tom Tromey
2012-09-12 20:00 ` Khoo Yit Phang
2012-09-13 20:56 ` Tom Tromey
2012-09-13 21:51 ` Khoo Yit Phang
2012-09-14 5:48 ` Regression for --batch [Re: [RFC] Make python/lib/gdb and submodules proper Python modules] Jan Kratochvil
2012-09-14 6:00 ` Khoo Yit Phang
2012-09-14 6:16 ` Jan Kratochvil [this message]
2012-09-14 6:26 ` Khoo Yit Phang
2012-09-14 6:37 ` Jan Kratochvil
2012-09-14 6:53 ` Khoo Yit Phang
2012-09-14 7:04 ` 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=20120914061549.GA6011@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=khooyp@cs.umd.edu \
--cc=tromey@redhat.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