zhq0918,

Seg faults most commonly occur when the library was compiled with one configuration but the application using the library has a different configuration. Yesterday I had recommended you add a setting to the Linux SGX makefile, please add the same define to the wolfssl-examples/SGX_Linux/sgx_t.mk and sgx_u.mk to ensure the application is configured the same as the library.

Warm Regards,

K

Hi @zhq0918,

If the seg fault is not due to misconfiguration the next thing to check is dereferencing a NULL variable in any way IE let's say a malloc failed and a variable wasn't checked against NULL after the malloc but application code later uses the variable which was never allocated.

If that proves not to be the case check for variable use after a free IE a variable was malloced, used, freed, used again (after the free).

A third thing to check is reading out of bounds IE is there any application code that accesses or modifies memory outside of a variable (buffer overflow/underflow).

Last thing to check is your stack and heap inside the enclave. If the stack and heap are colliding one could be over-writing the other causing corruptions in either stack or heap which can result in a segmentation fault.

Regards,

K