On Wed, Sep 13, 2023 at 06:11:46PM +0200, Lukas Mai wrote: > I don't know about stack transitions, but the XS code gets called from the > keyword plugin interface (from the parser), and it then calls back into Perl > at compile time. Normally, XS code gets calls from pp_entersub, which is in a runops loop, which is either at the top-level or has been invoked from something like call_sv(). In those circumstances the XS code would be automatically 'wrapped' and old-style XS code would run just fine. Your XS code getting called from the keyword plugin interface is an unusual route and thus is somehow not getting wrapped, and most likely implies that I need to look into it and ensure that that route gets handled correctly by the perl core too. I'll add it to my list of things to look into. -- Decaffeinated coffee is like dehydrated waterThread Previous | Thread Next