On 11 February 2012 14:55, Tim Bunce <tim.bu...@pobox.com> wrote: > On Fri, Feb 10, 2012 at 04:48:38PM -0800, Jan Dubois wrote: >> MSVCRT!abort >> perl514!PerlEnvGetenv+0x13 [perlhost.h @ 462] >> DBI!dbi_bootinit+0x276 [DBI.xs @ 468] >> DBI!XS_DBI__clone_dbis+0x71 [DBI.c @ 4280] >> >> Anyways, I would suggest trying a workaround by moving the getenv() >> call outside the cloning operation. > > Hopefully the above will do the trick. Meanwhile, aborting if getenv is > called during a CLONE sure seems like a bug worthy of a ticket for p5p.
I am not so sure. During a clone, the internals are potentially in an indeterminate state. I could see it being argued that the only thing you should be doing during a clone is cloning, not environment lookups. But of course, if we can fix it that would be better. And the above is pure speculation. Yves -- perl -Mre=debug -e "/just|another|perl|hacker/"
