[strongSwan] charon dies and leaves core file

[Tobias Brunner]

Hi Brad,

> I have caused charon to die 3 more times now with strongSwan splitdebug 
> enabled. Each time the stack trace is a little different. The common 
> things for all of them are thread #1 is in segv_handler with signal=11, 
> and gdb reports at least one of the threads having a possible corrupt 
> stack. Here's the latest full backtrace for all 21 threads.

Thread 1's backtrace doesn't look great either.  But as you probably
guessed this doesn't help much in determining the actual reason for the
crash.

Is the crash fully reproducible?  Does it always happen at the same
point?  Could you post the complete daemon log leading up to a crash?

Does Gentoo delete binaries of a previous version when upgrading a
package?  If you changed the plugin configuration for the new build you
should probably check if there are older plugins (that you haven't
enabled in the new build) still installed.  They might still get loaded
due to the modular plugin loading.

Regards,
Tobias