Hi Quincy,
I'll be pulling pieces out of the large c++ project into a small test c
program to see if the seg fault can be duplicated in a wieldable example
and if accomplished, will send it to you.
MemoryScape and gdb(Netbeans) doesn't show any memory issues from our
library code and hdf5.
Hi Quincey, [got the 'e' this time]
The problem cannot be repeated in a c example program because the
problem is upstream use of vector's with a -= operation. The failure in
this area did not show except in this mpi application even though the
same library and code is used in single
Hi Roger,
On Dec 8, 2010, at 11:41 AM, Roger Martin wrote:
Hi Quincey, [got the 'e' this time]
The problem cannot be repeated in a c example program because the problem is
upstream use of vector's with a -= operation. The failure in this area did
not show except in this mpi
Further:
Debugging with MemoryScape:
Reveals a segfault in H5SL.c (1.8.5) at line 1068
...1068
H5SL_REMOVE(SCALAR, slist, x, const haddr_t, key, -)
//H5SL_TYPE_HADDR case
The stack trace is:
H5SL_remove 1068
H5C_flush_single_entry 7993
Hi Roger,
On Dec 7, 2010, at 2:06 PM, Roger Martin wrote:
Further:
Debugging with MemoryScape:
Reveals a segfault in H5SL.c (1.8.5) at line 1068
...1068
H5SL_REMOVE(SCALAR, slist, x, const haddr_t, key, -)
//H5SL_TYPE_HADDR case
The stack trace is:
H5SL_remove
