PySPICE fails to install

[fergalm]

I'm having some trouble getting PySpice installed on my machine.
It compiles without warning:

$ CSPICE_SRC=/home/fmullall/apps/cspice/
$ export CSPICE_SRC
$ python setup.py build_ext
running build_ext
building '_spice' extension
creating build
creating build/temp.linux-x86_64-2.7
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/home/fmullall/apps/cspice/include -I/usr/include/python2.7 -c pyspice.c -o build/temp.linux-x86_64-2.7/pyspice.o
gcc -pthread -fno-strict-aliasing -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -DNDEBUG -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2 -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64 -mtune=generic -D_GNU_SOURCE -fPIC -fwrapv -fPIC -I/home/fmullall/apps/cspice/include -I/usr/include/python2.7 -c spicemodule.c -o build/temp.linux-x86_64-2.7/spicemodule.o
creating build/lib.linux-x86_64-2.7
gcc -pthread -shared build/temp.linux-x86_64-2.7/pyspice.o build/temp.linux-x86_64-2.7/spicemodule.o -L/home/fmullall/apps/cspice/lib -L/usr/lib64 -lcspice -lpython2.7 -o build/lib.linux-x86_64-2.7/_spice.so

and installs without incident:
$ python setup.py install --prefix=~/.local/
running install
running build
running build_py
creating build/lib.linux-x86_64-2.7/spice
copying spice/objects.py -> build/lib.linux-x86_64-2.7/spice
copying spice/init.py -> build/lib.linux-x86_64-2.7/spice
copying spice/misc.py -> build/lib.linux-x86_64-2.7/spice
running build_ext
running install_lib
copying build/lib.linux-x86_64-2.7/_spice.so -> /home/fmullall/.local//lib64/python2.7/site-packages
running install_egg_info
Removing /home/fmullall/.local//lib64/python2.7/site-packages/Spice-1.0-py2.7.egg-info
Writing /home/fmullall/.local//lib64/python2.7/site-packages/Spice-1.0-py2.7.egg-info

But when I run it, I get an error message:
$ PYTHONPATH=$PYTHONPATH:/home/fmullall/.local/lib64/python2.7/site-packages/
$ python -c 'import spice'
Traceback (most recent call last):
File "", line 1, in
File "spice/init.py", line 3, in
from misc import *
File "spice/misc.py", line 3, in
from _spice import *
ImportError: dynamic module does not define init function (init_spice)

The readme files suggests this might be a 32/64 bit problem, but cspice
is compiling 64 bit as well, as best I can tell. Any ideas what I'm doing wrong?

[michaelaye]

what do you mean by "cspice is compiling 64 bit as well' ? Are you compiling your own cspice? I am asking because usually NAIF delivers usable binaries in its distribution files?

[astromancer]

Hi there!

I'm bumping into exactly the same problem described above. I'm running the 64bit Linux SPICE (http://naif.jpl.nasa.gov/naif/toolkit_C_PC_Linux_GCC_64bit.html) and python 2.7.

I also tried Apollo117's Python3 fork, but again got the same error.

Any advice?

[fergalm]

Hi Apodemus,

Firstly, apologies to Michael Aye, for some reason I never saw your email
back when I was trying to get things installed. For what it's worth, I
think I downloaded source code and complied it myself, but I can't be sure.

Anyway, I fixed the missing init function error, but this was a couple of
years ago, and my memory is hazy about what I did exactly. I think the
solution was to follow the manual instructions in README.rst

I think the line
python mkwrapper.py /path/to/cspice > spicemodule.c

hardcoded a path to a shared object library previously generated by CSpice
so that python knew where to look for it.

Hope that helps.

Fergal

On 6 August 2014 05:48, apodemus [email protected] wrote:

Hi there!

I'm bumping into exactly the same problem described above. I'm running the
64bit Linux SPICE (
http://naif.jpl.nasa.gov/naif/toolkit_C_PC_Linux_GCC_64bit.html) and
python 2.7.

I also tried Apollo117's Python3 fork, but again got the same error.

Any advice?

—
Reply to this email directly or view it on GitHub
#6 (comment).

[astromancer]

Hi Fergal

The manual build did the trick. So simple - should have done that straight away!

Thanks!

[abieler]

Have the same thing happening. Can not do the manual install as

python mkwrapper.py /myPathTo/PySPICE-master/cspice > spicemodule.c

fails with

File "mkwrapper.py", line 1077, in
print main(cspice_toolkit)
File "mkwrapper.py", line 1004, in main
if gen_wrapper(curr_prototype, buffer):
File "mkwrapper.py", line 259, in gen_wrapper
param_info = parse_param(param)
File "mkwrapper.py", line 837, in parse_param
raise msg
ValueError: invalid literal for int() with base 10: ''

I had pyspice working on several machines under linux, but with mint 17 it now fails.
sidenote: when executing python setup.py build_ext it returns the same error as above, however rerunning the command will let it go through. also the install part works with no complaints.

cheers
andre

[drbitboy]

Quick solution for N0065:

https://github.com/drbitboy/PySPICE

[abieler]

thanks, that worked fine. Although some funky permission issues:

/usr/local/lib/python2.7/dist-packages/spice/ and _spice.so had reading permissions
disabled. so python could not import it although it was installed just fine.

[matteobachetti]

I have the same problem.
The fix (manual installation with hardcoded full path) didn't work for me, on Ubuntu 14.04 LTS 64b and Mac OSX Mavericks (still 64b).
Funky things happen with the parsing of include files in mkwrapper.py.
In the file cspice/include/SpiceZpr.h, the line

                                SpiceDouble           termpts [ ][3] );

seems to give problems, producing in turn that

ValueError: invalid literal for int() with base 10: ''

message. That open bracket/space/closed bracket raises an exception in mkwrapper.py. Eliminating the space doesn't seem to take the problem away.

This does not happen in linux 32b AFAIK, as other colleagues installed it correctly, but I haven't had the time to install it on a VM and test it myself.

[drbitboy]

Quick solution for N0065:

https://github.com/drbitboy/PySPICE

[drjmcauliffe]

@drbitboy thanks for this fix.

[tonyVeco]

I have problems after installing PySPICE for linux suse 32 bit to use SPICE in the 32 bit version.
The spice package correctly appears in the python library but I can not use any of the functions, python does not recognize them. What could be the problem?

[michaelaye]

Please specify "appears in the python library". Do you mean "import spice"
worked?
And what do you mean by "python does not recognize them".
Just show the commands you are trying to do and their error messages.

On Mon, Mar 16, 2015 at 8:47 AM, antonio19812 [email protected]
wrote:

I have problems after installing PySPICE for linux suse 32 bit to use
SPICE in the 32 bit version.
The spice package correctly appears in the python library but I can not
use any of the functions, python does not recognize them. What could be the
problem?

—
Reply to this email directly or view it on GitHub
#6 (comment).

[tonyVeco]

This is the screenshot.
I need to work with spice and I am trying to learn how to use it. First I would like to try some examples of the various functions. I need to use for example GETFOV and I was trying to reproduce an example from the documentation but when I try to call the function and load the kernel with FURNSH, python just see them as undefined variables. WHY?? how should i call the functions??? I usually works with python but this time i have problems

[drjmcauliffe]

This wrapper of SPICE is not really maintained. I'd checkout SpiceyPy by Andrew Annex if I were you: https://github.com/AndrewAnnex/SpiceyPy

[drbitboy]

Do this at a shell prompt:

python -c 'import spice;spice.tkvrsn("toolkit")'

please and paste the result in a response here.

[drbitboy]

whoops that should be:

python -c 'import spice;print(spice.tkvrsn("toolkit"))'

[tonyVeco]

This is what I got on the shell prompt:

antonio@linux-zrhc:~> python -c 'import spice;print(spice.tkvrsn("toolkit"))'
Traceback (most recent call last):
File "", line 1, in
File "/usr/lib/python2.7/site-packages/spice/init.py", line 3, in
from misc import *
File "/usr/lib/python2.7/site-packages/spice/misc.py", line 3, in
from _spice import *
ImportError: dynamic module does not define init function (init_spice)

If you will help me it would be great...

[drbitboy]

I'll do my best

try this command:

nm -e path/to/_spice.so | grep init

and post the results again.

I don't know where your _spice.so file will be; for me it is in

build/lib.linux*/

under the top of the PySPICE/ area, but it is also in

~/.local/lib/python2.7/site-packages/_spice.so

[tonyVeco]

the result is :
nm: 'path/to/_spice.so': No such file

[drbitboy]

you have to figure out what "path/to/" is.

[tonyVeco]

and how can I do it? i am getting confused !!!

[drbitboy]

there is a file called _spice.so, it has been installed on your system, the "path/to/" is the directory where it resides. You need to figure out what that directory is. e.g. try

nm -e /usr/lib/python2.7/site-packages/_spice.so | grep init

?

[tonyVeco]

It is exactly in the site-packages directory!! I found it before reading your post but I could not enter here!!
What was wrong with the first installation? I did all that was in the instructions

[drbitboy]

I used "path/to/" as a placeholder for you to replace.

what was the result of the nm ... grep command?

[tonyVeco]

here is the result :

00002ee8 t __frame_dummy_init_array_entry
0000095c T _init

[michaelaye]

Actually, if you need the GETFOV function, you might indeed be better of with SpiceyPy, because our PySpice implementation does not yet encompass all available SPICE functions. @johnnycakes79 could confirm, if GETFOV works with SpiceyPy. I have a github version of PySpice that has GETFOV working as well, and maybe Brian's version works as well, but I don't remember if we ever merged it into here?

[tonyVeco]

Actually I have to use various function from Spice, not GETFOV but GETFOV can help me to understand some key elements of spice and the kernels..I did not know SpiceyPy, I have been told only about PySpice.

[drbitboy]

Your PySPICE did not build correctly, something is missing.

1. you need a symlink, named cspice, to the top of the NAIF cspice tree

2. python setup.py install

If you want to do a google hangout I can watch and coach you through it.

[tonyVeco]

This is what I did..
I downloaded the CSpice.tar.Z file for linux and I uncompressed it in the terminal with tar xfzv

then I put the Cspice uncompressed folder in the PySPICE-master folder that is obtained by uncompressing the PySpice-master.zip ..and then I followed the instructions of the readme file..

[drbitboy]

hmm, that should have worked.

try using my PySPICE (https://github.com/drbitboy/PySPICE), put in cspice, then

rm -R ./build
python setup.py build
python tests/test_btc.py

[tonyVeco]

I will try those lines. The kernel is the main part if I want to start using the routines...

[tonyVeco]

the line :

find . | sort

gives in the terminal as output all the possible files in the python workspace (the name for Eclipse of the directory where I save my python projects and the files to read).

Of course the Spicey package is not in the workspace directory but I added it in the PYTHONPATH and then in python with the line

import SpiceyPy as sp

sp.furnsh('example.ti')

python can not find the kernel.

Sorry for the question but the lines :

kernels/
kernels/example.ti
src/
src/test_getfov.py

should be executed in the SpiceyPy-master directory ?

[tonyVeco]

Executing the line:

antonio@linux-zrhc:~> find / kernels

the directory has not been found

[drbitboy]

I was setting up a hypothetical (and leaving out a lot of details that I think of as obvious) where the top directory (not /, but something like /home/antonio/getfovtestingdirectory/) has two sub-directories in it, kernels/ and src/, the kernels/ sub-dir has example.ti in it, and the src/ sub-dir has test_getfov.py in it.

it was just a hypothetical to make the point that the single string argument to the .furnsh call needed the same full path to example.ti, e.g. (../kernels/example.ti) in it that you would need if you were browsing, using more, the the contents of example.ti from the src/ sub-dir:

$ cd src/
$ more ../kernels/example.ti

the listing of files (kernels/, kernels/example.ti, src/, etc. - btw, they should all be prefixed with a ./) was the output of the 'find | sort' command in the sample directory & file structure I created.

[tonyVeco]

I did not understand, it is just my fault. The problem is my lack of knowledge about Linux stuff and that makes me confused also with the other elements. I have worked with python in and its packages in windows for 4 months with results and no problems. The situations is worse now in Linux for me. So I need the full path to the kernel example.ti The problem is how can I find it? executing the 'find | sort' instruction I did not see the kernels directory in the list. It is surely my fault, no doubt about it

[drbitboy]

Try this:

https://github.com/drbitboy/spgfovtest

[drbitboy]

okay, you are young and probably only heard the Ancient Songs of DOS from dinosaurs like me.

When in Linux (actually Unix(tm)), the term "path" refers to a directory (equivalent of "folder" in Windows terminology) or to a file.

When traversing directory trees, there are two types of paths, absolute and relative:

Absolute paths start with a slash (/), which by itself refers to the root directory of the system.

Relative paths start with something other than a slash, and are relative to your Current Working Directory (CWD)

An absolute path to a file is good because it will work no matter what your CWD is; an absolute path is brittle because it will fail to work if the path down the directory tree it embodies is changed.

A relative path to a file is good because it allows you to move an entire sub-directory tree around without having to re-code absolute paths, and the file will normally only be accessed from certain CWDs in that tree; a relative path will sometimes fail if you are not in the CWD from which it was designed to work.

Special for a directory tree: ../ is the directory above your CWD, ../../ is two directories above, etc.

That is a very brief and incomplete definition of path but it should get you started; you should probably look something up that is more thorough and/or in your native language (and I am not acting superior there; your English is much better than my Italian!).

Ciao, ragazz'!

[drbitboy]

Funny story:

I once deleted the .. directory using a GUI file manager, in an early version of AIX, as root. Within minutes I could not ls or do many other normal shell operations. Then our network manager comes in and asks me why my system was trying do delete files from the NFS servers (unsuccessfully; user root becomes user nobody with almost no permissions in certain cases). When he said that, the light came on and I hit the power switch.

[tonyVeco]

Oh my god your script works!!!! I have to undersrtand..._I will not sleep until I will have understood everything :))) I will offer you an italian pizza, a true one!!

[tonyVeco]

I also tried the examples from other functions, the problem is always the same, the routines could work but Python can not load the kernels...so I have to find where they are LOL

[drbitboy]

A true pizza? I am going to start looking for conferences I can attend in Italy!

[drbitboy]

Are the examples the SpiceyPy tests?

I also tried the examples from other functions, the problem is always the same, the routines could
work but Python can not load the kernels...so I have to find where they are LOL

[drjmcauliffe]

Are you using a metakernel to load your kernels? If so could you post it here.

[drbitboy]

not for nothing, but i find putting the meta-kernel into the Python source is a nice hack that keeps things like tests more self-contained (anything with external kernels is always going to be messy, but one less file would be nice).

sp.furnsh(__file__)

For some tests of text kernels (e.g. IKs, FKs) it should be possible to put the kernel pool variables into the Python source:

"""
\begindata
  FRAME_NH_LORRI = -98300
  [...]
\begintext
"""

[tonyVeco]

So ary for answering so late, I nhad unexpected problem with the connection at home, and I could not answer today while working. I will answer now to all the questions

[tonyVeco]

First answer for @drbitboy : the examples I am referring to are the ones in the documentation of each spice routine. I have no tried the SpiceyPy tests.Should I?

[tonyVeco]

For @drbitboy and @johnnycakes79 : I try to give a detailed explanation of the situation at the moment.
The SpiceyPy package is correctly installed, such as writing:

import SpiceyPy as sp

I can access to all the routines and writing

sp.

I obtained the list of all the functions with their short explanation.

The SpiceyPy package is installed in the Site-Packages directory, under the Python 2.7 interpreter that is the one I am currently using.

Thanks to @drbitboy and @johnnycakes79 I noticed the spicey tests in the folder "test" of the directory SpiceyPy-master and by terminal I executed both.
The first was the gettestkernels.py , with this output :

antonio@linux-zrhc:~/Programs/SpiceyPy-master/test> python gettestkernels.py
Checking for kernels...

Downloading: vg200022.tsc
Downloading: earth_topo_050714.tf
Downloading: earthstns_itrf93_050714.bsp
Downloading: earth_720101_070426.bpc

Done writing test meta kernel.
Downloading: vg200022.tsc
Downloading: earth_topo_050714.tf
Downloading: earthstns_itrf93_050714.bsp
Downloading: earth_720101_070426.bpc

All the kernels showed are downloaded in the "test" folder and not in my current working directory, there is also a test meta-kernel file called : testKernels.txt and it has this structure :

\begindata
KERNELS_TO_LOAD = (
'/home/antonio/Programs/SpiceyPy-master/test/pck00010.tpc'
'/home/antonio/Programs/SpiceyPy-master/test/de421.bsp'
'/home/antonio/Programs/SpiceyPy-master/test/gm_de431.tpc'
'/home/antonio/Programs/SpiceyPy-master/test/naif0011.tls'
)
\begintext

This is the only metakernel I can find, answering to @johnnycakes79 .

I also executed the second test called test_wrapper.py and thi is the output :

antonio@linux-zrhc:/Programs/SpiceyPy-master/test> python test_wrapper.py
Traceback (most recent call last):
File "test_wrapper.py", line 2, in
import pytest
ImportError: No module named pytest
antonio@linux-zrhc:/Programs/SpiceyPy-master/test>

all that said, what should I do?? what should I put in my working directory to access all the standard kernels??

[drbitboy]

pytest is a generic Python testing framework. You need to install it on your system.

if you are debian-based, this might work:

sudo apt-get install python-pytest

or if RedHat/CentOS:

yum install python-pytest

?

[tonyVeco]

I am working with OpenSuse 13.2 that should be close to RedHat if I am not wrong, so I will try that one...
By the way if you really come to Italy one original pizza will be yours for sure, I would be honoured with that..and of course the same is for @johnnycakes79

[drbitboy]

AndrewAnnex wrote:

[...]I have the installation scripts for SpiceyPy download a fresh copy of the toolkit for the user when doing an install.

Yes, we wrote a similar script for PySPICE some time ago (January, 2013).

[tonyVeco]

sorry I was wrong the Yum line is not the one for opensuse, I have installed pytest with:

pip -U pytest

and it was succesfully installed

Now i try again the test_wrapper.py

[tonyVeco]

I executed this line :

linux-zrhc:/home/antonio/Programs/SpiceyPy-master/test # python test_wrapper.py

and there was no output just the command line

linux-zrhc:/home/antonio/Programs/SpiceyPy-master/test #

what does it mean?

[drbitboy]

CHDIR (cd) to the top of the SpiceyPy directory tree and do this:

python setup.py test

[tonyVeco]

I have done it..I post the giant result :

linux-zrhc:/home/antonio/Programs/SpiceyPy-master/test # cd..
linux-zrhc:/home/antonio/Programs/SpiceyPy-master # python setup.py test
running test
running egg_info
writing requirements to SpiceyPy.egg-info/requires.txt
writing SpiceyPy.egg-info/PKG-INFO
writing top-level names to SpiceyPy.egg-info/top_level.txt
writing dependency_links to SpiceyPy.egg-info/dependency_links.txt
reading manifest file 'SpiceyPy.egg-info/SOURCES.txt'
writing manifest file 'SpiceyPy.egg-info/SOURCES.txt'
running build_ext
Checking for kernels...

Downloading: vg200022.tsc
Downloading: earth_topo_050714.tf
Downloading: earthstns_itrf93_050714.bsp
Downloading: earth_720101_070426.bpc

Done writing test meta kernel.
==================================================== test session starts =====================================================
platform linux2 -- Python 2.7.8 -- py-1.4.26 -- pytest-2.6.4
collected 545 items

test/testKernels.txt .
test/test_wrapper.py ...........................................................................................................................*** Error in `python': free(): invalid next size (fast): 0x0a49bfb0 ***
======= Backtrace: =========
/lib/libc.so.6(+0x6d7e3)[0xb746a7e3]
/lib/libc.so.6(+0x7392a)[0xb747092a]
/lib/libc.so.6(+0x7458d)[0xb747158d]
/usr/lib/libpython2.7.so.1.0(PyMem_Free+0x1b)[0xb7692f4b]
/usr/lib/python2.7/lib-dynload/_ctypes.so(+0x55d6)[0xb66f25d6]
/usr/lib/python2.7/lib-dynload/_ctypes.so(+0x5630)[0xb66f2630]
/usr/lib/libpython2.7.so.1.0(+0xa797f)[0xb766c97f]
/usr/lib/libpython2.7.so.1.0(+0x9a68d)[0xb765f68d]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x3aa)[0xb767bd0a]
/usr/lib/libpython2.7.so.1.0(+0x9b08e)[0xb766008e]
/usr/lib/libpython2.7.so.1.0(PyObject_Call+0x54)[0xb765afa4]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x20ee)[0xb767779e]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x392)[0xb767bcf2]
/usr/lib/libpython2.7.so.1.0(+0x9b08e)[0xb766008e]
/usr/lib/libpython2.7.so.1.0(PyObject_Call+0x54)[0xb765afa4]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x20ee)[0xb767779e]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x26f9)[0xb7677da9]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x26f9)[0xb7677da9]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x138)[0xb767ba98]
/usr/lib/libpython2.7.so.1.0(+0x9b08e)[0xb766008e]
/usr/lib/libpython2.7.so.1.0(PyObject_Call+0x54)[0xb765afa4]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x20ee)[0xb767779e]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x392)[0xb767bcf2]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0xccb)[0xb767637b]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x26f9)[0xb7677da9]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x392)[0xb767bcf2]
/usr/lib/libpython2.7.so.1.0(+0x9b08e)[0xb766008e]
/usr/lib/libpython2.7.so.1.0(PyObject_Call+0x54)[0xb765afa4]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x20ee)[0xb767779e]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x26f9)[0xb7677da9]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x26f9)[0xb7677da9]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x138)[0xb767ba98]
/usr/lib/libpython2.7.so.1.0(+0x9b08e)[0xb766008e]
/usr/lib/libpython2.7.so.1.0(PyObject_Call+0x54)[0xb765afa4]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x20ee)[0xb767779e]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x392)[0xb767bcf2]
/usr/lib/libpython2.7.so.1.0(+0x9b08e)[0xb766008e]
/usr/lib/libpython2.7.so.1.0(PyObject_Call+0x54)[0xb765afa4]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x20ee)[0xb767779e]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x392)[0xb767bcf2]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0xccb)[0xb767637b]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x392)[0xb767bcf2]
/usr/lib/libpython2.7.so.1.0(+0x9b08e)[0xb766008e]
/usr/lib/libpython2.7.so.1.0(PyObject_Call+0x54)[0xb765afa4]
/usr/lib/libpython2.7.so.1.0(+0x96d21)[0xb765bd21]
/usr/lib/libpython2.7.so.1.0(PyObject_Call+0x54)[0xb765afa4]
/usr/lib/libpython2.7.so.1.0(PyEval_CallObjectWithKeywords+0x89)[0xb7675219]
/usr/lib/libpython2.7.so.1.0(PyInstance_New+0x215)[0xb765cce5]
/usr/lib/libpython2.7.so.1.0(PyObject_Call+0x54)[0xb765afa4]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x1384)[0xb7676a34]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x392)[0xb767bcf2]
/usr/lib/libpython2.7.so.1.0(+0x9b08e)[0xb766008e]
/usr/lib/libpython2.7.so.1.0(PyObject_Call+0x54)[0xb765afa4]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x20ee)[0xb767779e]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x138)[0xb767ba98]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0xccb)[0xb767637b]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x392)[0xb767bcf2]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0xccb)[0xb767637b]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalCodeEx+0x392)[0xb767bcf2]
/usr/lib/libpython2.7.so.1.0(+0x9b08e)[0xb766008e]
/usr/lib/libpython2.7.so.1.0(PyObject_Call+0x54)[0xb765afa4]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x20ee)[0xb767779e]
/usr/lib/libpython2.7.so.1.0(PyEval_EvalFrameEx+0x26f9)[0xb7677da9]
======= Memory map: ========
08048000-08049000 r-xp 00000000 00:20 1732 /usr/bin/python2.7
08049000-0804a000 r--p 00000000 00:20 1732 /usr/bin/python2.7
0804a000-0804b000 rw-p 00001000 00:20 1732 /usr/bin/python2.7
09fc6000-0abe5000 rw-p 00000000 00:00 0 [heap]
af0db000-af0fe000 r-xp 00000000 00:20 1281 /lib/libtinfo.so.5.9
af0fe000-af0ff000 ---p 00023000 00:20 1281 /lib/libtinfo.so.5.9
af0ff000-af101000 r--p 00023000 00:20 1281 /lib/libtinfo.so.5.9
af101000-af104000 rw-p 00025000 00:20 1281 /lib/libtinfo.so.5.9
af104000-af105000 rw-p 00000000 00:00 0
af105000-af3ed000 r-xp 00000000 08:03 9343153 /home/antonio/Programs/SpiceyPy-master/SpiceyPy/spice.so
af3ed000-af3ee000 r--p 002e7000 08:03 9343153 /home/antonio/Programs/SpiceyPy-master/SpiceyPy/spice.so
af3ee000-af404000 rw-p 002e8000 08:03 9343153 /home/antonio/Programs/SpiceyPy-master/SpiceyPy/spice.so
af404000-b4bf6000 rw-p 00000000 00:00 0
b4bf6000-b4c46000 r-xp 00000000 00:20 129756 /usr/lib/python2.7/site-packages/numpy/random/mtrand.so
b4c46000-b4c47000 r--p 0004f000 00:20 129756 /usr/lib/python2.7/site-packages/numpy/random/mtrand.so
b4c47000-b4c7d000 rw-p 00050000 00:20 129756 /usr/lib/python2.7/site-packages/numpy/random/mtrand.so
b4c7d000-b4c7e000 rw-p 00000000 00:00 0
b4c7e000-b4cf7000 r-xp 00000000 00:20 59908 /usr/lib/libquadmath.so.0.0.0
b4cf7000-b4cf8000 r--p 00078000 00:20 59908 /usr/lib/libquadmath.so.0.0.0
b4cf8000-b4cf9000 rw-p 00079000 00:20 59908 /usr/lib/libquadmath.so.0.0.0
b4cf9000-b5277000 r-xp 00000000 00:20 120879 /usr/lib/lapack/liblapack.so.3.5.0
b5277000-b5278000 r--p 0057d000 00:20 120879 /usr/lib/lapack/liblapack.so.3.5.0
b5278000-b527b000 rw-p 0057e000 00:20 120879 /usr/lib/lapack/liblapack.so.3.5.0
b527b000-b5408000 rw-p 00000000 00:00 0
b5410000-b5449000 r-xp 00000000 00:20 1282 /lib/libreadline.so.6.2
b5449000-b544a000 r--p 00039000 00:20 1282 /lib/libreadline.so.6.2
b544a000-b544d000 rw-p 0003a000 00:20 1282 /lib/libreadline.so.6.2
b544d000-b5c8f000 rw-p 00000000 00:00 0
b5caf000-b5ccd000 r-xp 00000000 00:20 129692 /usr/lib/python2.7/site-packages/numpy/linalg/_umath_linalg.so
b5ccd000-b5cce000 r--p 0001e000 00:20 129692 /usr/lib/python2.7/site-packages/numpy/linalg/_umath_linalg.so
b5cce000-b5ccf000 rw-p 0001f000 00:20 129692 /usr/lib/python2.7/site-packages/numpy/linalg/_umath_linalg.so
b5ccf000-b630f000 rw-p 00000000 00:00 0
b632d000-b6348000 r-xp 00000000 00:20 1210 /lib/libgcc_s.so.1
b6348000-b6349000 r--p 0001a000 00:20 1210 /lib/libgcc_s.so.1
b6349000-b634a000 rw-p 0001b000 00:20 1210 /lib/libgcc_s.so.1
b634a000-b6449000 r-xp 00000000 00:20 86834 /usr/lib/libgfortran.so.3.0.0
b6449000-b644a000 r--p 000fe000 00:20 86834 /usr/lib/libgfortran.so.3.0.0
b644a000-b644b000 rw-p 000ff000 00:20 86834 /usr/lib/libgfortran.so.3.0.0
b644b000-b649d000 r-xp 00000000 00:20 98008 /usr/lib/blas/libblas.so.3.5.0
b649d000-b649e000 r--p 00051000 00:20 98008 /usr/lib/blas/libblas.so.3.5.0
b649e000-b649f000 rw-p 00052000 00:20 98008 /usr/lib/blas/libblas.so.3.5.0
b64a6000-b64aa000 r-xp 00000000 00:20 19780 /usr/lib/python2.7/lib-dynload/readline.so
b64aa000-b64ab000 r--p 00003000 00:20 19780 /usr/lib/python2.7/lib-dynload/readline.so
b64ab000-b64ac000 rw-p 00004000 00:20 19780 /usr/lib/python2.7/lib-dynload/readline.so
b64ac000-b64b4000 r-xp 00000000 00:20 129630 /usr/lib/python2.7/site-packages/numpy/fft/fftpack_lite.so
b64b4000-b64b5000 r--p 00007000 00:20 129630 /usr/lib/python2.7/site-packages/numpy/fft/fftpack_lite.so
b64b5000-b64b6000 rw-p 00008000 00:20 129630 /usr/lib/python2.7/site-packages/numpy/fft/fftpack_lite.so
b64b6000-b64b7000 r-xp 00000000 00:20 19717 /usr/lib/python2.7/lib-dynload/future_builtins.so
b64b7000-b64b8000 r--p 00000000 00:20 19717 /usr/lib/python2.7/lib-dynload/future_builtins.so
b64b8000-b64b9000 rw-p 00001000 00:20 19717 /usr/lib/python2.7/lib-dynload/future_builtins.so
b64b9000-b64bc000 r-xp 00000000 00:20 129695 /usr/lib/python2.7/site-packages/numpy/linalg/lapack_lite.so
b64bc000-b64bd000 r--p 00002000 00:20 129695 /usr/lib/python2.7/site-packages/numpy/linalg/lapack_lite.so
b64bd000-b64be000 rw-p 00003000 00:20 129695 /usr/lib/python2.7/site-packages/numpy/linalg/lapack_lite.so
b64be000-b64c4000 r-xp 00000000 00:20 129640 /usr/lib/python2.7/site-packages/numpy/lib/_compiled_base.so
b64c4000-b64c5000 r--p 00005000 00:20 129640 /usr/lib/python2.7/site-packages/numpy/lib/_compiled_base.so
b64c5000-b64c6000 rw-p 00006000 00:20 129640 /usr/lib/python2.7/site-packages/numpy/lib/_compiled_base.so
b64c6000-b64f2000 r-xp 00000000 00:20 129415 /usr/lib/python2.7/site-packages/numpy/core/scalarmath.so
b64f2000-b64f3000 r--p 0002b000 00:20 129415 /usr/lib/python2.7/site-packages/numpy/core/scalarmath.so
b64f3000-b64f4000 rw-p 0002c000 00:20 129415 /usr/lib/python2.7/site-packages/numpy/core/scalarmath.so
b64f4000-b6505000 r-xp 00000000 00:20 19772 /usr/lib/python2.7/lib-dynload/cPickle.so
b6505000-b6506000 r--p 00011000 00:20 19772 /usr/lib/python2.7/lib-dynload/cPickle.so
b6506000-b6507000 rw-p 00012000 00:20 19772 /usr/lib/python2.7/lib-dynload/cPickle.so
b6507000-b656c000 r-xp 00000000 00:20 129424 /usr/lib/python2.7/site-packages/numpy/core/umath.so
b656c000-b656d000 r--p 00064000 00:20 129424 /usr/lib/python2.7/site-packages/numpy/core/umath.so
b656d000-b6570000 rw-p 00065000 00:20 129424 /usr/lib/python2.7/site-packages/numpy/core/umath.so
b6570000-b6572000 rw-p 00000000 00:00 0
b6572000-b66d9000 r-xp 00000000 00:20 129406 /usr/lib/python2.7/site-packages/numpy/core/multiarray.so
b66d9000-b66da000 ---p 00167000 00:20 129406 /usr/lib/python2.7/site-packages/numpy/core/multiarray.so
b66da000-b66db000 r--p 00167000 00:20 129406 /usr/lib/python2.7/site-packages/numpy/core/multiarray.so
b66db000-b66e2000 rw-p 00168000 00:20 129406 /usr/lib/python2.7/site-packages/numpy/core/multiarray.so
b66e2000-b66eb000 rw-p 00000000 00:00 0
b66ec000-b66ed000 rwxp 00000000 00:00 0
b66ed000-b670a000 r-xp 00000000 00:20 19778 /usr/lib/python2.7/lib-dynload/_ctypes.so
b670a000-b670b000 r--p 0001c000 00:20 19778 /usr/lib/python2.7/lib-dynload/_ctypes.so
b670b000-b670e000 rw-p 0001d000 00:20 19778 /usr/lib/python2.7/lib-dynload/_ctypes.so
b670e000-b6930000 rw-p 00000000 00:00 0
b6930000-b6933000 r-xp 00000000 00:20 19781 /usr/lib/python2.7/lib-dynload/termios.so
b6933000-b6934000 r--p 00002000 00:20 19781 /usr/lib/python2.7/lib-dynload/termios.so
b6934000-b6936000 rw-p 00003000 00:20 19781 /usr/lib/python2.7/lib-dynload/termios.so
b6936000-b6ab6000 rw-p 00000000 00:00 0
b6ab6000-b6aeb000 r--s 00000000 00:11 15471 /run/nscd/dbflptxB (deleted)
b6aeb000-b6b2b000 rw-p 00000000 00:00 0
b6b2b000-b6b2d000 r-xp 00000000 00:20 19742 /usr/lib/python2.7/lib-dynload/dl.so
b6b2d000-b6b2e000 r--p 00001000 00:20 19742 /usr/lib/python2.7/lib-dynload/dl.so
b6b2e000-b6b2f000 rw-p 00002000 00:20 19742 /usr/lib/python2.7/lib-dynload/dl.so
b6b2f000-b6baf000 rw-p 00000000 00:00 0
b6baf000-b6c44000 r-xp 00000000 00:20 19756 /usr/lib/python2.7/lib-dynload/unicodedata.so
b6c44000-b6c45000 r--p 00094000 00:20 19756 /usr/lib/python2.7/lib-dynload/unicodedata.so
b6c45000-b6c58000 rw-p 00095000 00:20 19756 /usr/lib/python2.7/lib-dynload/unicodedata.so
b6c58000-b6d19000 rw-p 00000000 00:00 0
b6d19000-b6d24000 r-xp 00000000 00:20 19730 /usr/lib/python2.7/lib-dynload/parser.so
b6d24000-b6d25000 r--p 0000a000 00:20 19730 /usr/lib/python2.7/lib-dynload/parser.so
b6d25000-b6d26000 rw-p 0000b000 00:20 19730 /usr/lib/python2.7/lib-dynload/parser.so
b6d26000-b6d29000 r-xp 00000000 00:20 19776 /usr/lib/python2.7/lib-dynload/_locale.so
b6d29000-b6d2a000 r--p 00003000 00:20 19776 /usr/lib/python2.7/lib-dynload/_locale.so
b6d2a000-b6d2b000 rw-p 00004000 00:20 19776 /usr/lib/python2.7/lib-dynload/_locale.so
b6d2b000-b6d6b000 rw-p 00000000 00:00 0
b6d6b000-b6d7b000 r-xp 00000000 00:20 19758 /usr/lib/python2.7/lib-dynload/datetime.so
b6d7b000-b6d7c000 r--p 0000f000 00:20 19758 /usr/lib/python2.7/lib-dynload/datetime.so
b6d7c000-b6d7f000 rw-p 00010000 00:20 19758 /usr/lib/python2.7/lib-dynload/datetime.so
b6d7f000-b6d83000 r-xp 00000000 00:20 19737 /usr/lib/python2.7/lib-dynload/zlib.so
b6d83000-b6d84000 r--p 00003000 00:20 19737 /usr/lib/python2.7/lib-dynload/zlib.so
b6d84000-b6d85000 rw-p 00004000 00:20 19737 /usr/lib/python2.7/lib-dynload/zlib.so
b6d85000-b6dc5000 rw-p 00000000 00:00 0
b6dc5000-b6dc7000 r-xp 00000000 00:20 19782 /usr/lib/python2.7/lib-dynload/_bisect.so
b6dc7000-b6dc8000 r--p 00001000 00:20 19782 /usr/lib/python2.7/lib-dynload/_bisect.so
b6dc8000-b6dc9000 rw-p 00002000 00:20 19782 /usr/lib/python2.7/lib-dynload/_bisect.so
b6dc9000-b6e49000 rw-p 00000000 00:00 0
b6e49000-b6e4d000 r-xp 00000000 00:20 19765 /usr/lib/python2.7/lib-dynload/select.so
b6e4d000-b6e4e000 r--p 00003000 00:20 19765 /usr/lib/python2.7/lib-dynload/select.so
b6e4e000-b6e50000 rw-p 00004000 00:20 19765 /usr/lib/python2.7/lib-dynload/select.so
b6e50000-b6e57000 r-xp 00000000 00:20 19761 /usr/lib/python2.7/lib-dynload/_struct.so
b6e57000-b6e58000 r--p 00006000 00:20 19761 /usr/lib/python2.7/lib-dynload/_struct.so
b6e58000-b6e5a000 rw-p 00007000 00:20 19761 /usr/lib/python2.7/lib-dynload/_struct.so
b6e5a000-b6e5d000 r-xp 00000000 00:20 19735 /usr/lib/python2.7/lib-dynload/time.so
b6e5d000-b6e5e000 r--p 00002000 00:20 19735 /usr/lib/python2.7/lib-dynload/time.so
b6e5e000-b6e60000 rw-p 00003000 00:20 19735 /usr/lib/python2.7/lib-dynload/time.so
b6e60000-b6e63000 r-xp 00000000 00:20 19732 /usr/lib/python2.7/lib-dynload/fcntl.so
b6e63000-b6e64000 r--p 00002000 00:20 19732 /usr/lib/python2.7/lib-dynload/fcntl.so
b6e64000-b6e65000 rw-p 00003000 00:20 19732 /usr/lib/python2.7/lib-dynload/fcntl.so
b6e65000-b6e67000 r-xp 00000000 00:20 19729 /usr/lib/python2.7/lib-dynload/_random.so
b6e67000-b6e68000 r--p 00002000 00:20 19729 /usr/lib/python2.7/lib-dynload/_random.so
b6e68000-b6e69000 rw-p 00003000 00:20 19729 /usr/lib/python2.7/lib-dynload/_random.so
b6e69000-b6ea9000 rw-p 00000000 00:00 0
b6ea9000-b6ec3000 r-xp 00000000 00:20 19754 /usr/lib/python2.7/lib-dynload/_io.so
b6ec3000-b6ec4000 r--p 00019000 00:20 19754 /usr/lib/python2.7/lib-dynload/_io.so
b6ec4000-b6ecc000 rw-p 0001a000 00:20 19754 /usr/lib/python2.7/lib-dynload/_io.so
b6ecc000-b6ee1000 r-xp 00000000 00:20 1168 /lib/libz.so.1.2.8
b6ee1000-b6ee2000 r--p 00014000 00:20 1168 /lib/libz.so.1.2.8
b6ee2000-b6ee3000 rw-p 00015000 00:20 1168 /lib/libz.so.1.2.8
b6ee3000-b70ad000 r-xp 00000000 00:20 1295 /lib/libcrypto.so.1.0.0
b70ad000-b70ae000 ---p 001ca000 00:20 1295 /lib/libcrypto.so.1.0.0
b70ae000-b70bd000 r--p 001ca000 00:20 1295 /lib/libcrypto.so.1.0.0
b70bd000-b70c5000 rw-p 001d9000 00:20 1295 /lib/libcrypto.so.1.0.0
b70c5000-b70c8000 rw-p 00000000 00:00 0
b70c8000-b7121000 r-xp 00000000 00:20 1285 /lib/libssl.so.1.0.0
b7121000-b7123000 r--p 00059000 00:20 1285 /lib/libssl.so.1.0.0
b7123000-b7126000 rw-p 0005b000 00:20 1285 /lib/libssl.so.1.0.0
b7126000-b7129000 r-xp 00000000 00:20 19757 /usr/lib/python2.7/lib-dynload/_hashlib.so
b7129000-b712a000 r--p 00003000 00:20 19757 /usr/lib/python2.7/lib-dynload/_hashlib.so
b712a000-b712b000 rw-p 00004000 00:20 19757 /usr/lib/python2.7/lib-dynload/_hashlib.so
b712b000-b712f000 r-xp 00000000 00:20 19755 /usr/lib/python2.7/lib-dynload/binascii.so
b712f000-b7130000 r--p 00003000 00:20 19755 /usr/lib/python2.7/lib-dynload/binascii.so
b7130000-b7131000 rw-p 00004000 00:20 19755 /usr/lib/python2.7/lib-dynload/binascii.so
b7131000-b7138000 r-xp 00000000 00:20 19733 /usr/lib/python2.7/lib-dynload/math.so
b7138000-b7139000 r--p 00006000 00:20 19733 /usr/lib/python2.7/lib-dynload/math.so
b7139000-b713b000 rw-p 00007000 00:20 19733 /usr/lib/python2.7/lib-dynload/math.so
b713b000-b713e000 r-xp 00000000 00:20 19722 /usr/lib/python2.7/lib-dynload/cStringIO.so
b713e000-b713f000 r--p 00002000 00:20 19722 /usr/lib/python2.7/lib-dynload/cStringIO.so
b713f000-b7140000 rw-p 00003000 00:20 19722 /usr/lib/python2.7/lib-dynload/cStringIO.so
b7140000-b7147000 r-xp 00000000 00:20 19743 /usr/lib/python2.7/lib-dynload/_ssl.so
b7147000-b7148000 r--p 00006000 00:20 19743 /usr/lib/python2.7/lib-dynload/_ssl.so
b7148000-b7149000 rw-p 00007000 00:20 19743 /usr/lib/python2.7/lib-dynload/_ssl.so
b7149000-b71aa000 rw-p 00000000 00:00 0
b71aa000-b71b8000 r-xp 00000000 00:20 19723 /usr/lib/python2.7/lib-dynload/_socket.so
b71b8000-b71b9000 r--p 0000d000 00:20 19723 /usr/lib/python2.7/lib-dynload/_socket.so
b71b9000-b71be000 rw-p 0000e000 00:20 19723 /usr/lib/python2.7/lib-dynload/_socket.so
b71be000-b71c6000 r-xp 00000000 00:20 19753 /usr/lib/python2.7/lib-dynload/array.so
b71c6000-b71c7000 r--p 00007000 00:20 19753 /usr/lib/python2.7/lib-dynload/array.so
b71c7000-b71c9000 rw-p 00008000 00:20 19753 /usr/lib/python2.7/lib-dynload/array.so
b71c9000-b7209000 rw-p 00000000 00:00 0
b7209000-b720b000 r-xp 00000000 00:20 19734 /usr/lib/python2.7/lib-dynload/_functools.so
b720b000-b720c000 r--p 00001000 00:20 19734 /usr/lib/python2.7/lib-dynload/_functools.so
b720c000-b720d000 rw-p 00002000 00:20 19734 /usr/lib/python2.7/lib-dynload/_functools.so
b720d000-b7216000 r-xp 00000000 00:20 19726 /usr/lib/python2.7/lib-dynload/itertools.so
b7216000-b7217000 r--p 00008000 00:20 19726 /usr/lib/python2.7/lib-dynload/itertools.so
b7217000-b721b000 rw-p 00009000 00:20 19726 /usr/lib/python2.7/lib-dynload/itertools.so
b721b000-b7222000 r-xp 00000000 00:20 19752 /usr/lib/python2.7/lib-dynload/operator.so
b7222000-b7223000 r--p 00006000 00:20 19752 /usr/lib/python2.7/lib-dynload/operator.so
b7223000-b7225000 rw-p 00007000 00:20 19752 /usr/lib/python2.7/lib-dynload/operator.so
b7225000-b722b000 r-xp 00000000 00:20 19727 /usr/lib/python2.7/lib-dynload/_collections.so
b722b000-b722c000 r--p 00005000 00:20 19727 /usr/lib/python2.7/lib-dynload/_collections.so
b722c000-b722d000 rw-p 00006000 00:20 19727 /usr/lib/python2.7/lib-dynload/_collections.so
b722d000-b72ad000 rw-p 00000000 00:00 0
b72ad000-b72ec000 r--p 00000000 00:20 58112 /usr/lib/locale/en_US.utf8/LC_CTYPE
b72ec000-b73ad000 rw-p 00000000 00:00 0
b73ad000-b73f1000 r-xp 00000000 00:20 1169 /lib/libm-2.19.so
b73f1000-b73f2000 r--p 00043000 00:20 1169 /lib/libm-2.19.so
b73f2000-b73f3000 rw-p 00044000 00:20 1169 /lib/libm-2.19.so
b73f3000-b73f5000 r-xp 00000000 00:20 1280 /lib/libutil-2.19.so
b73f5000-b73f6000 r--p 00001000 00:20 1280 /lib/libutil-2.19.so
b73f6000-b73f7000 rw-p 00002000 00:20 1280 /lib/libutil-2.19.so
b73f7000-b73f8000 rw-p 00000000 00:00 0
b73f8000-b73fb000 r-xp 00000000 00:20 1155 /lib/libdl-2.19.so
b73fb000-b73fc000 r--p 00002000 00:20 1155 /lib/libdl-2.19.so
b73fc000-b73fd000 rw-p 00003000 00:20 1155 /lib/libdl-2.19.so
b73fd000-b75a3000 r-xp 00000000 00:20 1278 /lib/libc-2.19.so
b75a3000-b75a5000 r--p 001a6000 00:20 1278 /lib/libc-2.19.so
b75a5000-b75a6000 rw-p 001a8000 00:20 1278 /lib/libc-2.19.so
b75a6000-b75a9000 rw-p 00000000 00:00 0
b75a9000-b75c1000 r-xp 00000000 00:20 1224 /lib/libpthread-2.19.so
b75c1000-b75c2000 r--p 00017000 00:20 1224 /lib/libpthread-2.19.so
b75c2000-b75c3000 rw-p 00018000 00:20 1224 /lib/libpthread-2.19.so
b75c3000-b75c5000 rw-p 00000000 00:00 0
b75c5000-b770f000 r-xp 00000000 00:20 22690 /usr/lib/libpython2.7.so.1.0
b770f000-b7710000 r--p 00149000 00:20 22690 /usr/lib/libpython2.7.so.1.0
b7710000-b773f000 rw-p 0014a000 00:20 22690 /usr/lib/libpython2.7.so.1.0
b773f000-b7749000 rw-p 00000000 00:00 0
b7749000-b774c000 r-xp 00000000 00:20 19720 /usr/lib/python2.7/lib-dynload/_heapq.so
b774c000-b774d000 r--p 00002000 00:20 19720 /usr/lib/python2.7/lib-dynload/_heapq.so
b774d000-b774f000 rw-p 00003000 00:20 19720 /usr/lib/python2.7/lib-dynload/_heapq.so
b774f000-b7751000 r-xp 00000000 00:20 19769 /usr/lib/python2.7/lib-dynload/grp.so
b7751000-b7752000 r--p 00001000 00:20 19769 /usr/lib/python2.7/lib-dynload/grp.so
b7752000-b7753000 rw-p 00002000 00:20 19769 /usr/lib/python2.7/lib-dynload/grp.so
b7753000-b7758000 r-xp 00000000 00:20 19724 /usr/lib/python2.7/lib-dynload/strop.so
b7758000-b7759000 r--p 00004000 00:20 19724 /usr/lib/python2.7/lib-dynload/strop.so
b7759000-b775b000 rw-p 00005000 00:20 19724 /usr/lib/python2.7/lib-dynload/strop.so
b775b000-b7762000 r--s 00000000 00:20 58519 /usr/lib/gconv/gconv-modules.cache
b7762000-b7763000 rw-p 00000000 00:00 0
b7763000-b7764000 r-xp 00000000 00:00 0 [vdso]
b7764000-b7766000 r--p 00000000 00:00 0 [vvar]
b7766000-b7786000 r-xp 00000000 00:20 1174 /lib/ld-2.19.so
b7786000-b7787000 r--p 00020000 00:20 1174 /lib/ld-2.19.so
b7787000-b7788000 rw-p 00021000 00:20 1174 /lib/ld-2.19.so
bfadc000-bfafd000 rw-p 00000000 00:00 0 [stack]
Aborted

[drbitboy]

try it again. i suspect a minor hiccup.

[tonyVeco]

The output is exactly the same. I wonder if it my fault , if I have done something wrong before..

[michaelaye]

Guys, as much as this help is appreciated, this is now a SpiceyPy install/use help and therefore not related to this Github issue at all. I suggest to move to Gitter?

[drjmcauliffe]

I agree with @michaelaye. Also @antonio19812 you should seek more local support from your ESAC supervisor... To me it seems he or she has really thrown you in the deep end and while your initiative is to be recognised you shouldn't have to spend so much of your short traineeship debugging install problems!

[tonyVeco]

Actually what I am trying to do , @johnnycakes79 , is to access the standard kernels because I would like to practice with Spice using the examples in the documentations , so that I can try various kind of input and see the output and so on..but for my project I talked with my supervisor and I have been told that the kernels I need are available only in the Planetary Archive and I downloaded them. So at the moment I think that I have everything to go on with my project, but at the same time it could be useful for me to have a complete configuration of SpiceyPy. No problem for me to move to Gitter for my problem.

[BordeauxDave]

Just to thank drbitboy: I was having exactly the same problem as antonio19812 and your fix solved me.
(my first step had been to download the Latest & Greatest version so I don't understand why I had to go to replace it with your fix, but I don't really care either -- on to using PySPICE as a part of https://github.com/nanograv/PINT !). Sincere thanks, David.