segfault in "nxtest.py hdf4"

[stuartcampbell]

Original reporter: Cpascual

Running nxtest.py with no arguments or with "xml" seems ok.
But when running "nxtest.py hdf4" I get a segmentation fault after or during the link test:

$ python nxstest.py hdf4
=== File NXtest.hdf
@NeXus_version: 4.2.0
@HDF_version: NCSA HDF Version 4.1 Release 4, December 2000
@file_name: NXtest.hdf
@file_time: 2009-02-23T17:29:19+01:00
entry NXentry
  @hugo: namenlos
  @cucumber: passion
  ch_data char 10
  i1_data uint8 4
    [0 1 2 3]
  i2_data int16 4
    [   0 1000 2000 3000]
  i4_data int32 4
    [      0 1000000 2000000 3000000]
  r4_data float32 5x4
  r8_data float64 5x4
    @ch_attribute: NeXus
    @i4_attribute: 42
    @r4_attribute: 3.14159274101
    @target: /entry/r8_data
  data NXdata
    r8_data float64 5x4
      -> /entry/r8_data
    comp_data int32 100x20
    flush_data int32 7
      [0 1 2 3 4 5 6]
  sample NXsample
    @target: /entry/sample
    ch_data char 12
link NXentry
  sample NXsample
    -> /entry/sample
  renLinkGroup NXsample
    -> /entry/sample
Segmentation fault

[stuartcampbell]

Original reporter: Cpascual

Probably related to this:
With 4.2rc4 now allowing general tests, I get FAILED for all HDF4-related tests (not only those python-related)
Same tests worked with rc2 and the same HDF4 installation.

[stuartcampbell]

Original reporter: Cpascual

On a different machine (SuSe 10.2) for which the HDF4 tests succeed, I get "skipped" for the Python+HDF test and if running "python nxstest hdf4" manually, I get a frozen console:

=== File NXtest.hdf
@NeXus_version: 4.2.0
@HDF_version: NCSA HDF Version 4.2 Release 1, February 17, 2005
@file_name: NXtest.hdf
@file_time: 2009-02-24T14:42:09+01:00
entry NXentry
  @hugo: namenlos
  @cucumber: passion
  ch_data char 10
  i1_data uint8 4
    [0 1 2 3]
  i2_data int16 4
    [   0 1000 2000 3000]
  i4_data int32 4
    [      0 1000000 2000000 3000000]
  r4_data float32 5x4
  r8_data float64 5x4
    @ch_attribute: NeXus
*** glibc detected *** /usr/bin/python: free(): invalid next size (fast): 0x0826c3d8 ***

[eugenwintersberger]

This issue is now nexusformat/python-nxs#4. Please continue commenting on the python-nxs issue tracker.