From: Khoo Yit Phang <khooyp@cs.umd.edu>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Khoo Yit Phang <khooyp@cs.umd.edu>,
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:00:00 -0000 [thread overview]
Message-ID: <B8F45A56-D29A-438F-9B15-1CF6BAD14B95@cs.umd.edu> (raw)
In-Reply-To: <20120914054758.GA5191@host2.jankratochvil.net>
Hi Jan,
On Sep 14, 2012, at 1:47 AM, Jan Kratochvil wrote:
> Hi Yit,
>
> On Thu, 13 Sep 2012 23:51:08 +0200, Khoo Yit Phang wrote:
>> Thanks, I've checked in the patch.
>
> $ ./gdb --batch
> 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.
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.
Yit
September 14, 2012
next prev parent reply other threads:[~2012-09-14 6:00 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 [this message]
2012-09-14 6:16 ` Jan Kratochvil
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=B8F45A56-D29A-438F-9B15-1CF6BAD14B95@cs.umd.edu \
--to=khooyp@cs.umd.edu \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--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