This sounds like a use-after-free. That memory is either poisoned by
the allocator, or re-allocated and used by something that memset() it.
You can try running under valgrind, if it's fast enough, or you can try
backporting the ASAN additions from these commits:
William,
You are right, gsh_calloc is getting invoked (even for 2.3 code).
Interestingly for the core we got in testing, has almost all the fields
filled with 0xFF. So wondering is it something to do with underneath glibc
or RHEL in general.
Here is the gdb o/p indicating the same.
(gdb) p
On 10/27/17 7:56 AM, Sachin Punadikar wrote:
Ganesha 2.3 got segfault with below :
[...]
After analyzing the core and related code found that - In "thr_decode_rpc_request" function, if call to SVC_RECV fails, then free_nfs_request is invoked to free the resources. But so far one of the field
Hello,
Ganesha 2.3 got segfault with below :
*Core was generated by `/usr/bin/ganesha.nfsd -L /var/log/ganesha.log -f
/etc/ganesha/ganesha.conf -N N'.Program terminated with signal 11,
Segmentation fault.#0 0x0044b4dd in free_nfs_request
(reqdata=0x7f19c5e48010)at
