My recollection is that that file_image interface is intended to provide ultimate control over memory allocation re-allocation, etc.
So, I believe it *should* be possible to do what you are attempting though I don't know the interface in detail enough to suggest options.
Mark
···
From: Iván Cores González <ivan.coresg@udc.es<mailto:ivan.coresg@udc.es>>
Reply-To: HDF Users Discussion List <hdf-forum@lists.hdfgroup.org<mailto:hdf-forum@lists.hdfgroup.org>>
Date: Friday, December 5, 2014 10:02 AM
To: "hdf-forum@lists.hdfgroup.org<mailto:hdf-forum@lists.hdfgroup.org>" <hdf-forum@lists.hdfgroup.org<mailto:hdf-forum@lists.hdfgroup.org>>
Subject: [Hdf-forum] Changing HF5get_file_image() behaviour with callbacks
Dear sir/madam,
I am working with HDF5 and the "HDF5 File Image Operations".
I write a HDF5 file in memory (using the H5FD_CORE driver) and after that
I recover a copy of the file with the HF5get_file_image() function.
Could be possible obtain the original memory (not a copy) using the
HF5set_file_image_callbacks function? It is possible redefine the
"image_malloc" and "image_memcpy" functions to avoid do a copy?
I am reading the documentation and I am not sure if it is possible ...
Yours faithfully,
Ivan Cores.
_______________________________________________
Hdf-forum is for HDF software users discussion.
Hdf-forum@lists.hdfgroup.org<mailto:Hdf-forum@lists.hdfgroup.org>
http://mail.lists.hdfgroup.org/mailman/listinfo/hdf-forum_lists.hdfgroup.org
Twitter: https://twitter.com/hdf5