----- "Ken McDonell" <kenj@xxxxxxxxxxxxxxxx> wrote:
> tzbuffer is a static and it does not really need to be ... we could
> malloc it and let it leak (or stay in the environment) ... I'll poke
> around a bit in that area.
>
> What remains a complete mystery is why/how the perl_destruct()
> routine
> finds out about this address at all when it does not leak back
> through
> the API wrapper into Perl-land ... which supports your (and my)
> original
> hypothesis that this is really a Perl stack corruption issue
> associated
> with the call and args from Perl or the return values to Perl, but
> alas we have not smoking gun there.
Perl does provide env variables within the runtime to scripts (ie
$ENV{TZ}) ... perhaps we have confused it a bit by making a new
variable appear spontaneously, esp. one like TZ which actually
means something to the system. It may be trying to teardown (via
an environ array walk? or a known "system" set perhaps) what it
thought it constructed initially ... just a guess though, and I
don't have the strength to dig through the core perl code. :)
cheers.
--
Nathan
|