On Mon, Jul 11, 2005 at 01:29:37PM +0100, Steve Hay wrote:
The patch below fixes it, and all tests still pass. Is it OK?
looks good to me
--
A power surge on the Bridge is rapidly and correctly diagnosed as a faulty
capacitor by the highly-trained and competent engineering staff.
--
Dave Mitchell wrote:
On Mon, Jul 11, 2005 at 01:29:37PM +0100, Steve Hay wrote:
The patch below fixes it, and all tests still pass. Is it OK?
looks good to me
Marvellous. Now applied.
Radan Computational Ltd.
The information
Dave Mitchell wrote:
On Fri, Jul 08, 2005 at 09:36:19AM +0100, Steve Hay wrote:
The crash is deliberately forced by win32_checkTLS(), but I don't
understand for what reason. PerlEnvGetenv() takes an IPerlEnv* and uses
the IPERL2HOST() macro (which is set to IPerlEnv2Host()) to locate the
On Fri, Jul 08, 2005 at 09:36:19AM +0100, Steve Hay wrote:
The crash is deliberately forced by win32_checkTLS(), but I don't
understand for what reason. PerlEnvGetenv() takes an IPerlEnv* and uses
the IPERL2HOST() macro (which is set to IPerlEnv2Host()) to locate the
CPerlHost* which that
Dave Mitchell wrote:
On Thu, Jul 07, 2005 at 01:56:39PM +0100, Steve Hay wrote:
Hmm. I just retried this with current blead and I find that it
(apparently) works OK with a debug build, but crashes with a release build.
I can't get it to crash on either type of build (Linux).
:-(
Dave Mitchell wrote:
On Thu, Feb 24, 2005 at 01:32:25PM +, Steve Hay wrote:
Stas Bekman wrote:
The following scalar leak is reproduced under any perl 5.8+ w/ithreads:
#!/usr/bin/perl -T
use Devel::Peek;
use threads;
local $0 = test; # == XXX: leaks scalar
my $thr =
On Thu, Jul 07, 2005 at 01:56:39PM +0100, Steve Hay wrote:
Hmm. I just retried this with current blead and I find that it
(apparently) works OK with a debug build, but crashes with a release build.
I can't get it to crash on either type of build (Linux).
Fortunately, release builds on
On Thu, Feb 24, 2005 at 01:32:25PM +, Steve Hay wrote:
Stas Bekman wrote:
The following scalar leak is reproduced under any perl 5.8+ w/ithreads:
#!/usr/bin/perl -T
use Devel::Peek;
use threads;
local $0 = test; # == XXX: leaks scalar
my $thr = threads-new(sub { Dump $0 });
# New Ticket Created by Stas Bekman
# Please include the string: [perl #34341]
# in the subject line of all future correspondence about this issue.
# URL: https://rt.perl.org/rt3/Ticket/Display.html?id=34341
This is a bug report for perl from [EMAIL PROTECTED],
generated with the help of
(resubmitting Steve Hay's followup so it'll be stored in rt)
Stas Bekman (via RT) wrote:
# New Ticket Created by Stas Bekman
# Please include the string: [perl #34341]
# in the subject line of all future correspondence about this issue.
# URL:
Stas Bekman wrote:
The following scalar leak is reproduced under any perl 5.8+ w/ithreads:
#!/usr/bin/perl -T
use Devel::Peek;
use threads;
local $0 = test; # == XXX: leaks scalar
my $thr = threads-new(sub { Dump $0 });
$thr-join;# == XXX: triggers the leak
[...]
Scalars leaked: 1
The following scalar leak is reproduced under any perl 5.8+ w/ithreads:
#!/usr/bin/perl -T
use Devel::Peek;
use threads;
local $0 = test; # == XXX: leaks scalar
my $thr = threads-new(sub { Dump $0 });
$thr-join;# == XXX: triggers the leak
% perl -T leak.pl
SV = PVMG(0x81129a0) at 0x816dc10
12 matches
Mail list logo
