Open yilongx opened 12 years ago
Calling setPolicyStatus() and getPolicy() have the same Phenomenon
Thank you for entering the issue. Unfortunately the current design will do this if the calls are not done in the right order, this is because the structures have not been set up. Agreed there should be some protection and it should not cause a segmentation fault.
Sorry, didn't mean to close the issue. It will remain open until it is resolved.
The issue still exists in the new version. although we should do test in order, when we do other test without initial LIB &
device, we think that it should tell us "it can't connect to Device".
“Segmentation fault” when i call setPolicy() with out-of-band mode without initial Lib and Device
The gdb trace info as follow:
(gdb) n 299 ret = nmprk::translation::setPolicy(d, policy); (gdb) n
Program received signal SIGSEGV, Segmentation fault. 0x000000000041c4fe in nmprk::ipmi::modules::nm_dcmi::nm_dcmi_remote_runIpmiCommand (d=0x7fffffffe270, req=0x7fffffffde80, rsp=0x7fffffffde60) at src/modules/nm_dcmi/linux/nm_dcmi_linux.cpp:295 295 lun = intf->target_lun; (gdb)