in reply to perlembed: perl_run twice?

I expect it is because on most systems, some of the C libraries are not re-entrant; particularly, memory allocation and I/O routines. This sounds like the same issue with signal handlers not being re-entrant covered in perlipc. The problems will likely manifest as core dumps.

NB: A re-entrant (thread safe) library protects its internal data structures from corruption due to the potential for simultaneous access.

cheers

tachyon