Hi Magnus,

Could you please send the HDF4 file to [email protected]? We will take a look. 
And which version of h4h5tools are you using?

Thank you!

Elena
On Mar 21, 2011, at 12:26 PM, Magnus Hagdorn wrote:

> Hi list,
> one of our users has reported an odd problem with the h4toh5 tool. On a 64bit 
> machine h4toh5 fails with
> *** stack smashing detected ***: h4toh5 terminated
> Aborted
> on 32bit it simply segfaults. h4h5tools pass the supplied test suite. The 
> older version of the h4h5tools works fine. On 32bit, I get the following 
> backtrace:
> 
> 
> 
> Program received signal SIGSEGV, Segmentation fault.
> 0x08073862 in H4toH5check_objname_in_use (h4toh5id=1684549234, h5par_path=0x0,
>    objname=0xbfffdb38 
> "/disk/scratch/local/mjf/clavrx/work/output/NSS.GHRR.NK.D02001.S1138.E1322.B1890102.WI.cmr.hdf")
>  at h4toh5main.c:1001
> 1001       used = 
> lookup_name(h4toh5id,h5_aboname,OBJECT_HASHSIZE,dt->name_hashtab);
> (gdb) bt
> #0  0x08073862 in H4toH5check_objname_in_use (h4toh5id=1684549234, 
> h5par_path=0x0,
>    objname=0xbfffdb38 
> "/disk/scratch/local/mjf/clavrx/work/output/NSS.GHRR.NK.D02001.S1138.E1322.B1890102.WI.cmr.hdf")
>  at h4toh5main.c:1001
> #1  0x080648a5 in H4toH5get_group_name (h4toh5id=1684549234, 
> vgroup_id=805306470, h5par_path=0x0) at h4toh5util.c:2706
> #2  0x6d632e49 in ?? ()
> #3  0x64682e72 in ?? ()
> #4  0x30000066 in ?? ()
> #5  0x00000000 in ?? ()
> (gdb)
> 
> 
> I had a look at the code but couldn't see any obvious problems. Does anyone 
> have any suggestions?
> 
> Cheers
> magnus
> 
> 
> 
> -- 
> The University of Edinburgh is a charitable body, registered in
> Scotland, with registration number SC005336.
> 
> 
> _______________________________________________
> Hdf-forum is for HDF software users discussion.
> [email protected]
> http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org


_______________________________________________
Hdf-forum is for HDF software users discussion.
[email protected]
http://mail.hdfgroup.org/mailman/listinfo/hdf-forum_hdfgroup.org

Reply via email to