Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.python > #72477
| From | dieter <dieter@handshake.de> |
|---|---|
| Subject | Re: ImportError: No module named _gdb |
| Date | 2014-06-03 08:11 +0200 |
| References | <431f3c0e-1cc3-43b2-91a0-34acf3b1da09@googlegroups.com> <mailman.10537.1401689257.18130.python-list@python.org> <9dced0b1-9423-4c61-b640-78a261b93637@googlegroups.com> |
| Newsgroups | comp.lang.python |
| Message-ID | <mailman.10597.1401775928.18130.python-list@python.org> (permalink) |
Marcelo Sardelich <msardelich@gmail.com> writes: > Didier thanks for your prompt reply. > I installed a pre-built version of Python. > As you said, probably something is missing. > > I tried to google packages related to gdb, but ain't had no luck. The missing part is related to the gdb-Python integration. Look around for information about this integration - e.g. installation instructions. What is missing is apparently a C extension for Python. When you have the source of this package, then it may contain a "setup.py". In this case "[sudo] python setup.py install" may do everything necessary to get a working C extension. > Do you have any idea if it is a compiler directive? Not for this problem. However, using "gdb" usually profits considerably from having debugging symbols. A system installed Python usually lacks those symbols. Therefore, after you have solved the current problem, it may be profitable to compile your own Python from source.
Back to comp.lang.python | Previous | Next — Previous in thread | Find similar | Unroll thread
ImportError: No module named _gdb Marcelo Sardelich <msardelich@gmail.com> - 2014-06-01 15:43 -0700
Re: ImportError: No module named _gdb dieter <dieter@handshake.de> - 2014-06-02 08:07 +0200
Re: ImportError: No module named _gdb Marcelo Sardelich <msardelich@gmail.com> - 2014-06-02 10:22 -0700
Re: ImportError: No module named _gdb dieter <dieter@handshake.de> - 2014-06-03 08:11 +0200
csiph-web