I think that's a different segfault than we've seen before.
It may be the same issue, but this time entirely in the shibboleth code.
My recommendation is that JISC report this through the Shibboleth
consortium and pursue it there.
The issue may be that by the time term is called some destructors within
log4shib have already been called.
|