On 13:27 Thu 16 Feb , Owen Stampflee wrote: > > Commenting out the cl_log_event in osm_log results in this backtrace: > > (gdb) bt > #0 0x00000080b9719db0 in .__GI_raise () from /lib64/tls/libc.so.6 > #1 0x00000080b971b89c in .__GI_abort () from /lib64/tls/libc.so.6 > #2 0x00000080b974e860 in .__libc_message () from /lib64/tls/libc.so.6 > #3 0x00000080b9756db0 in ._int_malloc () from /lib64/tls/libc.so.6 > #4 0x00000080b9758b50 in .__GI___libc_malloc () > from /lib64/tls/libc.so.6 > #5 0x00000400000607bc in __cl_malloc_priv (size=0) at > cl_memory_osd.c:62 > #6 0x00000400000604d4 in __cl_zalloc_ntrk (size=0) at cl_memory.c:416 > #7 0x00000400000629f4 in cl_ptr_vector_set_capacity > (p_vector=0x100788d0, > new_capacity=6349) at cl_ptr_vector.c:216
p_vector=0x100788d0 does not look like valid 64-bit address. Is it case that complib is not created properly (don't know how exactly, probably ./configured)? Sasha _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
