OpenHPI pool segv core

[Akijdarvajkar]

Observing occational core dump on a openHPI with following stack trace :

Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x0000000000000000 in ?? ()
[Current thread is 1 (Thread 0xffd2fff1d0 (LWP 15645))]
(gdb) bt
#0 0x0000000000000000 in ?? ()
#1 0x000000ffec6bb528 in oh_get_sensor_reading () from /lib/openhpi/libipmidirect.so
#2 0x000000012001f0bc in saHpiSensorReadingGet ()
#3 0x0000000120009e04 in process_msg(cHpiMarshal, int, char, unsigned int&, unsigned int&) ()#4 0x0000000120006f3c in service_thread(void, void) ()
warning: GDB can't find the start of the function at 0xffecb62ad3.

GDB is unable to find the start of the function at 0xffecb62ad3
and thus can't determine the size of that function's stack frame.
This means that GDB may be unable to access that stack frame, or
the frames below it.
This problem is most likely caused by an invalid program counter or
stack pointer.
However, if you think GDB should simply search farther back
from 0xffecb62ad3 for code which looks like the beginning of a
function, you can increase the range of the search using the `set
heuristic-fence-post' command.
#5 0x000000ffecb62ad4 in ?? () from /usr/lib64/libglib-2.0.so.0
(gdb)

As we can see that the stack trace is not clear and the only clue is oh_get_sensor_reading() called from ipmidirect library.

Compared for any fixes available in the latest OpenHPI 3.8.0 but looks like no changes or fixes.

Please let us know possible causes for the issue and any known issues? If there is any solution to get rid of the same.