On Fri, 2005-05-27 at 14:27, Tom Duffy wrote: > I just noticed that my opensm had segv'ed and dumped core. Here is the > gdb backtrace. > > #0 stack_dump () at src/stack.c:72 > 72 if (!__builtin_frame_address(2)) > (gdb) bt > #0 stack_dump () at src/stack.c:72 > #1 0x00002aaaaabb71a6 in handler (x=11) at src/stack.c:151 > #2 <signal handler called>
Looks like osm_dump_dr_smp was called with a NULL p_smp so: osm_madw_get_smp_ptr(p_madw) returned NULL for some unknown reason and that is an unexpected (should not occur) condition. > #3 osm_dump_dr_smp (p_log=0x552498, p_smp=0x0, log_level=32 ' ') > at osm_helper.c:1446 > #4 0x000000000042eed1 in __osm_vl15_poller (p_ptr=0x552498) at osm_madw.h:575 > #5 0x00002aaaaadc911e in __cl_thread_wrapper (arg=0x0) at cl_thread.c:61 > #6 0x00000036d28060aa in start_thread () from /lib64/tls/libpthread.so.0 > #7 0x00000036d19c53d3 in clone () from /lib64/tls/libc.so.6 > #8 0x0000000000000000 in ?? () Anything "special" about your configuration/what was going on ? Can you reproduce this ? Also, what version of OpenSM are you using ? -- Hal _______________________________________________ openib-general mailing list [email protected] http://openib.org/mailman/listinfo/openib-general To unsubscribe, please visit http://openib.org/mailman/listinfo/openib-general
