Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Michael Snyder <msnyder@vmware.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: python help(gdb) doesn't work in my local build.
Date: Fri, 11 Mar 2011 20:48:00 -0000	[thread overview]
Message-ID: <20110311204837.GA15389@host1.jankratochvil.net> (raw)
In-Reply-To: <4D7A7BCA.5000408@vmware.com>

On Fri, 11 Mar 2011 20:45:14 +0100, Michael Snyder wrote:
> No such file or directory: '/usr/local/share/gdb/python/gdb'
> 
> 1) What do I do to tell it where to look locally?
> 2) What do I do to install this by hand?

GDB is intentionally omitted from the standalone-Python help.

On correctly Fedora 14 x86_64 installed Python+GDB:

$ python -c 'help(gdb)'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
NameError: name 'gdb' is not defined
$ gdb -q -nx -ex 'python help(gdb)' -ex q
Help on package gdb:

NAME
    gdb
[...]

GDB part of the help was intentionally moved out of the standard Python help
directory tree as reading the code providing help texts requires to load the
whole such Python modules which require the bindings provided by GDB itself.

http://bugs.python.org/issue7015
https://bugzilla.redhat.com/show_bug.cgi?id=526313

$ python
>>> help()                                                                      help> modules gdb

Here is a list of matching modules.  Enter any module name to get more help.

Traceback (most recent call last):
<module>
    class RequireCommand (gdb.Command):
AttributeError: 'module' object has no attribute 'Command'



Regards,
Jan


      parent reply	other threads:[~2011-03-11 20:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-11 19:45 Michael Snyder
2011-03-11 20:39 ` Tom Tromey
2011-03-11 21:03   ` Michael Snyder
2011-03-11 21:52     ` Tom Tromey
2011-03-11 20:48 ` Jan Kratochvil [this message]

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=20110311204837.GA15389@host1.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=msnyder@vmware.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