Enache Adrian wrote: > Change 21589 broke it. > It adds a > PERL_SET_CONTEXT(proto_perl) > in the perl_clone_using function (sv.c:109999). > > So when the CLONE method from the DBI stash is called (at sv.c:11658), > it will get (via the dSP, etc macros) the PL_stack_base, PL_stack_sp > pointers _not_ from the new interpreter (my_perl), but from the old one > (the proto_perl in sv.c). > > Fortunately this should happen only with -DDEBUGGING builds. > > I have no idea why that PERL_SET_CONTEXT has been put there. The > change description says something about eggs and chickens. That kind > of problems go far beyond my understanding. Well, the original problem is at http://www.xray.mpe.mpg.de/mailing-lists/perl5-porters/2003-10/msg01449.html In fact what was wanted (and implemented by this patch) is the ability to access the PerlIO API early during the cloning -- to be used by debugging flags (-D) for example.Thread Previous | Thread Next