[Thread Prev][Thread Next][Index]

[ferret_users] : pyferret 7.2 segmentation fault when a second variable is displayed



Hi,

my new version of pyferret ends with an segmentation fault, when I am trying to display more than one variable.

See the example below. I have compiled pyferret by myself, so there may be, perhaps, some error in my installation of python, but the same python behaves well with earlier pyferret versions. The same error occurs with two different builds on different system version (openSuse 13.2 and SLES_11).

Below is an example with hycom data. Other data sets produce the same error. Does anyone else experience the same?

Best,

Martin



mschmidt@phy-59:~> ferret

        NOAA/PMEL TMAP
        PyFerret v7.2 (optimized)
        Linux 3.16.7-53-default - 07/15/17
        17-Jul-17 10:32

yes? use http://tds.hycom.org/thredds/dodsC/GLBu0.08/expt_91.2/ts3z
yes? sh data
     currently SET data sets:
    1> http://tds.hycom.org/thredds/dodsC/GLBu0.08/expt_91.2/ts3z (default)
 name     title                             I         J K         L
 TAU      Tau                              ...       ... ...       1:437
 WATER_TEMP
          Water Temperature                1:4500    1:2001 1:40      1:437
 SALINITY Salinity                         1:4500    1:2001 1:40      1:437

yes? shade/x=0/l=100 WATER_TEMP
yes? shade/x=0/l=100 SALINITY
Traceback (most recent call last):
  File "<string>", line 1, in <module>
File "/sw/viz/ferret/py_ferret_v720_os132_py_27/lib/python2.7/site-packages/pyferret/__init__.py", line 538, in init
    result = run()
File "/sw/viz/ferret/py_ferret_v720_os132_py_27/lib/python2.7/site-packages/pyferret/__init__.py", line 710, in run
    retval = libpyferret._run(str_command)
RuntimeError:

**ERROR Ferret crash; signal = 11 (SIGSEGV)
Enter Ctrl-D to exit Python


--
Dr. Martin Schmidt
Leibniz-Institute for Baltic Sea Research
Seestrasse 15
D18119 Rostock
Germany



[Thread Prev][Thread Next][Index]
Contact Us
Dept of Commerce / NOAA / OAR / PMEL / Ferret

Privacy Policy | Disclaimer | Accessibility Statement