[perl #37161] thread ignores :utf8 file i/o discipline

2005-09-13 Thread via RT
=2.4.21-32.0.1.elsmp, archname=i686-linux-thread-multi uname='linux pong.us.proofpoint.com 2.4.21-32.0.1.elsmp #1 smp tue may 17 17:52:23 edt 2005 i686 i686 i386 gnulinux ' config_args='' hint=recommended, useposix=true, d_sigaction=define usethreads=define use5005threads=undef

[perl #7565] Thread safe queues on SMP kernel

2005-07-14 Thread Michael G Schwern via RT
When run using 5.8.6 and ithreads perl thinks for a while and then sez: $ perl ~/tmp/test A thread exited while 4 threads were running. So this looks like an issue in Thread::Queue and not 5.005threads. Unless the sample code is not sane, but I don't know threads well enough to evaluate that.

[perl #18961] Problem compiling DBD::Pg with thread support in 5.8 on Mac OS 10.2.2

2005-07-14 Thread Michael G Schwern via RT
[radknee - Sun Dec 08 09:15:16 2002]: Using CPAN I did 'install DBD::PG'. Config went ok, but make produced the errors below. When I recompiled perl without threads make went ok. [systame1:local/src/DBD-Pg-1.13] randy% make cc -c -I/usr/local/pgsql/include -I/Library/Perl/darwin-thread

[perl #24407] perl crashes when usings 'exists $foo{}' with shared thread hash

2005-07-14 Thread Michael G Schwern via RT
[EMAIL PROTECTED] - Tue Nov 04 00:39:47 2003]: Perl crashes on the following test program: use threads; use threads::shared; my %hash : shared; exists $hash{1}; The error message is: 'Free to wrong pool 15d26e8 not 1aeb8f0.' From reading the discussion of this ticket it seems that

Re: [perl #7565] Thread safe queues on SMP kernel

2005-07-14 Thread Dave Mitchell
On Thu, Jul 14, 2005 at 01:24:22AM -0700, Michael G Schwern via RT wrote: When run using 5.8.6 and ithreads perl thinks for a while and then sez: $ perl ~/tmp/test A thread exited while 4 threads were running. So this looks like an issue in Thread::Queue and not 5.005threads. Unless

RE: [perl #19088] Thread::Queue

2005-07-06 Thread Lihn, Steve
It appears identical. I am not sure why I thought it is better. Sorry about it... Steve Lihn -Original Message- From: Michael G Schwern via RT [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 05, 2005 1:29 AM To: Lihn, Steve Subject: [perl #19088] Thread::Queue [EMAIL PROTECTED

Re: [perl #19088] Thread::Queue

2005-07-06 Thread Michael G Schwern
that if something empties @$q you still have $p to return. Best guess I can make not knowing much about Thread::Queue. The original is like: sub dequeue { my $q = shift; lock(@$q); cond_wait @$q until @$q; cond_signal @$q if @$q 1; return shift @$q

Re: [perl #19088] Thread::Queue

2005-07-06 Thread Dave Mitchell
relinquishing it during cond_wait). The cond_signal bit is only for the specific case that more than one item was pushed onto the queue, and that there is more than one consumer thread waiting to remove it: the first thread to get its snout in the trough signals to its compatriots (if any

Re: [perl #35895] Not OK: perl v5.8.7 +RC1 on darwin-thread-multi-2level 8.1.0 (UNINSTALLED)

2005-06-27 Thread Nicholas Clark
On Sun, Jun 05, 2005 at 12:41:04PM +0200, Dominic Dunlop wrote: Locale = eu_ES $VAR1 = { 'currency_symbol' = 'Eu', 'decimal_point' = '\' ', 'frac_digits' = 2, 'grouping' = '', 'int_curr_symbol' = 'EUR ', 'int_frac_digits' = 2,

Re: [perl #35925] GvHV() can end up pointing at garbage - thread dup bug

2005-06-22 Thread Nicholas Clark
On Sat, May 21, 2005 at 08:06:22PM +0100, Dave Mitchell wrote: On Sat, May 21, 2005 at 07:54:09PM +0100, Nicholas Clark wrote: Surely that logic is pants, in that: correct. :unique seems to be a badly-thought out hack. What happens if a child thread creates a new unique GV, spawns

[perl #36214] OK: perl v5.8.6 +23953 +33990 on darwin-thread-multi-2level 8.0

2005-06-08 Thread via RT
6) configuration: Platform: osname=darwin, osvers=8.0, archname=darwin-thread-multi-2level uname='darwin b28.apple.com 8.0 darwin kernel version 7.5.0: thu mar 3 18:48:46 pst 2005; root:xnuxnu-517.99.13.obj~1release_ppc power macintosh powerpc ' config_args='-ds -e -Dprefix=/usr

Re: [perl #35895] Not OK: perl v5.8.7 +RC1 on darwin-thread-multi-2level 8.1.0 (UNINSTALLED)

2005-06-06 Thread Nicholas Clark
On Sun, Jun 05, 2005 at 06:24:31PM +0200, Dominic Dunlop wrote: On 5 Jun 2005, at 13:33, John Peacock wrote: Dominic Dunlop wrote: Actually, I'm on the other side of the fence now (now that I looked at the code). It does appear that Perl intends to correctly handle other radix

Re: [perl #35895] Not OK: perl v5.8.7 +RC1 on darwin-thread-multi-2level 8.1.0 (UNINSTALLED)

2005-06-05 Thread Dominic Dunlop
On 5 Jun 2005, at 01:36, John Peacock wrote: I concur that this is probably something weird with the Apple implementation. I have a small script in my Math::Currency distro which extracts the currency information for different locales and this is what I see with SUSE 9.2's eu_ES:

Re: [perl #35895] Not OK: perl v5.8.7 +RC1 on darwin-thread-multi-2level 8.1.0 (UNINSTALLED)

2005-06-05 Thread John Peacock
Dominic Dunlop wrote: On 4 Jun 2005, at 20:40, Paul Schinder wrote: The question is, should perl be able to handle whatever is in that locale slot, even if it makes no sense, or at least give a more useful error message? I don't think it's reasonable to ask perl to do anything sensible or

Re: [perl #35895] Not OK: perl v5.8.7 +RC1 on darwin-thread-multi-2level 8.1.0 (UNINSTALLED)

2005-06-05 Thread Dominic Dunlop
On 5 Jun 2005, at 13:33, John Peacock wrote: Dominic Dunlop wrote: I don't think it's reasonable to ask perl to do anything sensible or helpful when presented with a decimal_point this silly. Actually, I'm on the other side of the fence now (now that I looked at the code). It does

Re: [perl #35895] Not OK: perl v5.8.7 +RC1 on darwin-thread-multi-2level 8.1.0 (UNINSTALLED)

2005-06-04 Thread Dominic Dunlop
of my perl5 (revision 5 version 8 subversion 7) configuration: Platform: osname=darwin, osvers=8.1.0, archname=darwin-thread-multi-2level uname='darwin g5.local 8.1.0 darwin kernel version 8.1.0: tue may 10 18:16:08 pdt 2005; root:xnu-792.1.5.obj~4release_ppc power macintosh powerpc

Re: [perl #35895] Not OK: perl v5.8.7 +RC1 on darwin-thread-multi-2level 8.1.0 (UNINSTALLED)

2005-06-04 Thread Paul Schinder
, archname=darwin-thread-multi-2level uname='darwin g5.local 8.1.0 darwin kernel version 8.1.0: tue may 10 18:16:08 pdt 2005; root:xnu-792.1.5.obj~4release_ppc power macintosh powerpc ' config_args='' hint=recommended, useposix=true, d_sigaction=define usethreads=define

Re: [perl #35895] Not OK: perl v5.8.7 +RC1 on darwin-thread-multi-2level 8.1.0 (UNINSTALLED)

2005-06-04 Thread Paul Schinder
Dominic Dunlop wrote: The issue here seems to be that the locale says that the radix separator (that is, the character used to separate the integer part of a number from the decimal fraction) for this locale is ', and perl can't cope. Here's a sample of the output from harness -v: I made

Re: [perl #35895] Not OK: perl v5.8.7 +RC1 on darwin-thread-multi-2level 8.1.0 (UNINSTALLED)

2005-06-04 Thread John Peacock
Paul Schinder wrote: It certainly seems to be Apple's bug. en_EU/LC_MONETARY shows ,, not ', for the monetary decimal point (if I'm reading it right; I compared it with en_US/LC_MONETARY). Checking some of the neighboring locale's (es_ES, fr_FR) LC_NUMERIC shows ,. I concur that this is

[perl #36114] Segfault when use encoding with thread

2005-06-03 Thread via RT
# New Ticket Created by Koichi Kimura # Please include the string: [perl #36114] # in the subject line of all future correspondence about this issue. # URL: https://rt.perl.org/rt3/Ticket/Display.html?id=36114 Hi, I use perl with sjis encoding. Segfault occures when use encoding with thread

[perl #36055] OK: perl v5.8.7 on i686-linux-thread-multi 2.4.18-bf2.4

2005-06-01 Thread via RT
subversion 7) configuration: Platform: osname=linux, osvers=2.4.18-bf2.4, archname=i686-linux-thread-multi uname='linux alexandra 2.4.18-bf2.4 #1 son apr 14 09:53:28 cest 2002 i686 unknown ' config_args='-des -Dusedevel -Uversiononly -Dmydomain=.abigail.nl [EMAIL PROTECTED] [EMAIL

[perl #36056] OK: perl v5.8.7 on i686-linux-thread-multi-64int-ld 2.4.18-bf2.4

2005-06-01 Thread via RT
subversion 7) configuration: Platform: osname=linux, osvers=2.4.18-bf2.4, archname=i686-linux-thread-multi-64int-ld uname='linux alexandra 2.4.18-bf2.4 #1 son apr 14 09:53:28 cest 2002 i686 unknown ' config_args='-des -Dusedevel -Uversiononly -Dmydomain=.abigail.nl [EMAIL PROTECTED] [EMAIL

[perl #36067] OK: perl v5.8.7 on i386-linux-thread-multi 2.6.10-1.771_fc2

2005-06-01 Thread via RT
) configuration: Platform: osname=linux, osvers=2.6.10-1.771_fc2, archname=i386-linux-thread-multi uname='linux phoenix.squirrel.nl 2.6.10-1.771_fc2 #1 mon mar 28 00:50:14 est 2005 i686 athlon i386 gnulinux ' config_args='-des -Darchname=i386-linux -Dprefix=/opt/perl-5.8.7 [EMAIL

[perl #36070] Not OK: perl v5.8.7 on darwin-thread-multi-2level 8.1.0 (UNINSTALLED)

2005-06-01 Thread via RT
configuration information for perl v5.8.7: Configured by schinder at Tue May 31 13:37:09 EDT 2005. Summary of my perl5 (revision 5 version 8 subversion 7) configuration: Platform: osname=darwin, osvers=8.1.0, archname=darwin-thread-multi-2level uname='darwin g5.local 8.1.0 darwin kernel

[perl #35925] GvHV() can end up pointing at garbage - thread dup bug

2005-05-21 Thread via RT
), strlen(HvNAME(gp-gp_hv)), then various thread-creating tests fail during global destruction: Failed Test Stat Wstat Total Fail Failed List of Failed --- ../ext/Storable/t/threads.t 29

Re: [perl #35925] GvHV() can end up pointing at garbage - thread dup bug

2005-05-21 Thread Dave Mitchell
(), which at clone time basically fills all unused slots (eg gv_hv) in the :unique GV with PL_sv_no from the *parent* thread: /* attempt to make everything in the typeglob readonly */ STATIC SV * S_gv_share(pTHX_ SV *sstr, CLONE_PARAMS *param) { GV *gv = (GV*)sstr; SV *sv

Re: [perl #35925] GvHV() can end up pointing at garbage - thread dup bug

2005-05-21 Thread Nicholas Clark
-create(sub { 1} )-join(); It seems to be down to the code in S_gv_share(), which at clone time basically fills all unused slots (eg gv_hv) in the :unique GV with PL_sv_no from the *parent* thread: Surely that logic is pants, in that: a: it should be PL_sv_no from the child thread and b: even

Re: [perl #35925] GvHV() can end up pointing at garbage - thread dup bug

2005-05-21 Thread Dave Mitchell
On Sat, May 21, 2005 at 07:54:09PM +0100, Nicholas Clark wrote: Surely that logic is pants, in that: correct. :unique seems to be a badly-thought out hack. a: it should be PL_sv_no from the child thread that would be an improvement b: even PL_sv_no is wrong, because too much other code

[perl #35895] Not OK: perl v5.8.7 +RC1 on darwin-thread-multi-2level 8.1.0 (UNINSTALLED)

2005-05-20 Thread via RT
subversion 7) configuration: Platform: osname=darwin, osvers=8.1.0, archname=darwin-thread-multi-2level uname='darwin g5.local 8.1.0 darwin kernel version 8.1.0: tue may 10 18:16:08 pdt 2005; root:xnu-792.1.5.obj~4release_ppc power macintosh powerpc ' config_args='' hint

[perl #35905] OK: perl v5.8.7 +RC1 on i686-linux-thread-multi 2.4.18-bf2.4

2005-05-20 Thread via RT
configuration information for perl v5.8.7: Configured by abigail at Sat May 21 01:36:45 CEST 2005. Summary of my perl5 (revision 5 version 8 subversion 7) configuration: Platform: osname=linux, osvers=2.4.18-bf2.4, archname=i686-linux-thread-multi uname='linux alexandra 2.4.18-bf2.4 #1

[perl #35906] OK: perl v5.8.7 +RC1 on i686-linux-thread-multi-64int-ld 2.4.18-bf2.4

2005-05-20 Thread via RT
subversion 7) configuration: Platform: osname=linux, osvers=2.4.18-bf2.4, archname=i686-linux-thread-multi-64int-ld uname='linux alexandra 2.4.18-bf2.4 #1 son apr 14 09:53:28 cest 2002 i686 unknown ' config_args='-des -Dusedevel -Uversiononly -Dmydomain=.abigail.nl [EMAIL PROTECTED] [EMAIL

[perl #34639] OK: perl v5.9.2 on darwin-thread-multi-2level 7.8.0 (UNINSTALLED)

2005-04-01 Thread via RT
subversion 2) configuration: Platform: osname=darwin, osvers=7.8.0, archname=darwin-thread-multi-2level uname='darwin g5.local 7.8.0 darwin kernel version 7.8.0: wed dec 22 14:26:17 pst 2004; root:xnuxnu-517.11.1.obj~1release_ppc power macintosh powerpc ' config_args='' hint

Re: Detecting thread exits

2005-01-25 Thread Eric Garland
Elizabeth Mattijsen wrote: At 11:18 AM -0500 1/24/05, Eric Garland wrote: I'm setting up a Boss/Worker threaded program that runs for a very long time. There are times where a worker thread will run into errors and exit. The obvios solution would be to prevent that from happening but I would

Re: Detecting thread exits

2005-01-25 Thread Elizabeth Mattijsen
At 11:56 AM -0500 1/25/05, Eric Garland wrote: Elizabeth Mattijsen wrote: You might want to have a look at Thread::Running on CPAN, by yours truly. Interesting approach. I found an issue in that an immediate call to running after starting a thread returns false ala: my $thread = threads-new

Detecting thread exits

2005-01-24 Thread Eric Garland
I'm setting up a Boss/Worker threaded program that runs for a very long time. There are times where a worker thread will run into errors and exit. The obvios solution would be to prevent that from happening but I would like to create a fault tolerant framework that doesn't tip over

Re: Detecting thread exits

2005-01-24 Thread Elizabeth Mattijsen
At 11:18 AM -0500 1/24/05, Eric Garland wrote: I'm setting up a Boss/Worker threaded program that runs for a very long time. There are times where a worker thread will run into errors and exit. The obvios solution would be to prevent that from happening but I would like to create a fault

Re: FAIL TermReadKey-2.30 MSWin32-x86-multi-thread 4.0

2005-01-18 Thread Steve Hay
Randy Kobes wrote: On Mon, 17 Jan 2005, Steve Hay wrote: [ .. ] Yes, $Config{[g]ccversion} should really hold the compiler version, but currently doesn't. I can fix that fairly easily for cl and gcc. (I don't know about Borland's compiler.) This well help in the future, so is worth doing,

recycling thread IDs

2005-01-17 Thread David Nicol
i noticed the threads documentation says that thread IDs count upwards to infinity. We could recycle old thread IDs in a FIFO way using a strategy similar to the indices in Array::Frugal. In short, when an ID is returned, it is placed at the top of the stack, and the stack of free IDs is managed

Re: FAIL TermReadKey-2.30 MSWin32-x86-multi-thread 4.0

2005-01-17 Thread Jonathan Stowe
On Fri, 2005-01-14 at 15:29, Steve Hay wrote: Jonathan Stowe wrote: On Fri, 2005-01-14 at 11:31, Jonathan Stowe wrote: On Thu, 2005-01-13 at 18:52, [EMAIL PROTECTED] wrote: GetConsoleMode failed, LastError=|6| at blib\lib/Term/ReadKey.pm line 265. END failed--call

Re: FAIL TermReadKey-2.30 MSWin32-x86-multi-thread 4.0

2005-01-17 Thread Steve Peters
On Mon, Jan 17, 2005 at 03:00:02PM +, Jonathan Stowe wrote: In principle would it be possible to determine the compiler and/or CRT version at configure time and make that available to test in cases like this? Ideally, the compiler version should be held in Config.pm in the ccversion or

Re: FAIL TermReadKey-2.30 MSWin32-x86-multi-thread 4.0

2005-01-17 Thread Steve Hay
Jonathan Stowe wrote: On Fri, 2005-01-14 at 15:29, Steve Hay wrote: The only solution that I've come up with in cases where sharing CRT resources in this way is unavoidable is to recommend that users use the same compiler to build my modules as was used to build Perl. I don't even have a

Re: recycling thread IDs

2005-01-17 Thread Dave Mitchell
On Mon, Jan 17, 2005 at 02:24:29AM -0600, David Nicol wrote: i noticed the threads documentation says that thread IDs count upwards to infinity. We could recycle old thread IDs in a FIFO way using a strategy similar to the indices in Array::Frugal. This would serve no purpose that I can see

Re: FAIL TermReadKey-2.30 MSWin32-x86-multi-thread 4.0

2005-01-17 Thread Steve Hay
Steve Hay wrote: Jonathan Stowe wrote: In principle would it be possible to determine the compiler and/or CRT version at configure time and make that available to test in cases like this? Yes, $Config{[g]ccversion} should really hold the compiler version, but currently doesn't. I can

Re: FAIL TermReadKey-2.30 MSWin32-x86-multi-thread 4.0

2005-01-17 Thread Randy Kobes
On Mon, 17 Jan 2005, Steve Hay wrote: [ .. ] Yes, $Config{[g]ccversion} should really hold the compiler version, but currently doesn't. I can fix that fairly easily for cl and gcc. (I don't know about Borland's compiler.) This well help in the future, so is worth doing, but clearly

Re: FAIL TermReadKey-2.30 MSWin32-x86-multi-thread 4.0

2005-01-14 Thread Jonathan Stowe
welcomed, especially testing with various MS compiler and Perl versions. Perl version: Summary of my perl5 (revision 5 version 8 subversion 4) configuration: Platform: osname=MSWin32, osvers=4.0, archname=MSWin32-x86-multi-thread uname='' config_args='undef' hint=recommended, useposix

Re: FAIL TermReadKey-2.30 MSWin32-x86-multi-thread 4.0

2005-01-14 Thread Steve Hay
Jonathan Stowe wrote: On Fri, 2005-01-14 at 11:31, Jonathan Stowe wrote: On Thu, 2005-01-13 at 18:52, [EMAIL PROTECTED] wrote: GetConsoleMode failed, LastError=|6| at blib\lib/Term/ReadKey.pm line 265. END failed--call queue aborted. NMAKE : fatal error U1077:

[perl #15189] Not OK: perl v5.8.0 on MSWin32-x86-multi-thread 4.0 (UNINSTALLED)

2004-12-01 Thread Steve Peters via RT
[sky - Sat Apr 26 03:02:29 2003]: Hi, Could you try the maint snapshot that is going to be 5.8.1 at http://www.iki.fi/jhi/[EMAIL PROTECTED] or http://www.iki.fi/jhi/[EMAIL PROTECTED] Thanks Arthur With Perl 5.8.6, I got none of the test failures mentioned in the original

[perl #22318] Not OK: perl v5.8.1 +MAINT19612 on MSWin32-x86-multi-thread 4.0 (UNINSTALLED)

2004-12-01 Thread Steve Peters via RT
[EMAIL PROTECTED] - Sun May 25 14:27:36 2003]: This is a build failure report for perl from [EMAIL PROTECTED], generated with the help of perlbug 1.34 running under perl v5.8.1. - [Please enter your report here] Testing

[perl #22318] Not OK: perl v5.8.1 +MAINT19612 on MSWin32-x86-multi-thread 4.0 (UNINSTALLED)

2004-12-01 Thread Steve Peters via RT
[stmpeters - Wed Dec 01 12:13:03 2004]: [EMAIL PROTECTED] - Sun May 25 14:27:36 2003]: This is a build failure report for perl from [EMAIL PROTECTED], generated with the help of perlbug 1.34 running under perl v5.8.1.

Re: [perl #22318] Not OK: perl v5.8.1 +MAINT19612 on MSWin32-x86-multi-thread 4.0 (UNINSTALLED)

2004-12-01 Thread Marcus Holland-Moritz
On 2004-12-02, at 04:29:47 -, Steve Peters via RT wrote: [stmpeters - Wed Dec 01 12:13:03 2004]: [EMAIL PROTECTED] - Sun May 25 14:27:36 2003]: This is a build failure report for perl from [EMAIL PROTECTED], generated with the help of perlbug 1.34 running under perl v5.8.1.

Re: [perl #22318] Not OK: perl v5.8.1 +MAINT19612 on MSWin32-x86-multi-thread 4.0 (UNINSTALLED)

2004-12-01 Thread Steve Peters
On Thu, Dec 02, 2004 at 06:14:20AM +0100, Marcus Holland-Moritz wrote: On 2004-12-02, at 04:29:47 -, Steve Peters via RT wrote: [stmpeters - Wed Dec 01 12:13:03 2004]: [EMAIL PROTECTED] - Sun May 25 14:27:36 2003]: This is a build failure report for perl from [EMAIL

[perl #32671] OK: perl v5.8.6 on i386-linux-thread-multi 2.6.8-1.521

2004-11-28 Thread via RT
) configuration: Platform: osname=linux, osvers=2.6.8-1.521, archname=i386-linux-thread-multi uname='linux phoenix.squirrel.nl 2.6.8-1.521 #1 mon aug 16 09:01:18 edt 2004 i686 athlon i386 gnulinux ' config_args='-des -Darchname=i386-linux -Dprefix=/opt/perl-5.8.6 [EMAIL PROTECTED

[perl #32664] OK: perl v5.8.6 on darwin-thread-multi-2level 7.6.0 (UNINSTALLED)

2004-11-27 Thread via RT
subversion 6) configuration: Platform: osname=darwin, osvers=7.6.0, archname=darwin-thread-multi-2level uname='darwin g5.local 7.6.0 darwin kernel version 7.6.0: sun oct 10 12:05:27 pdt 2004; root:xnuxnu-517.9.4.obj~1release_ppc power macintosh powerpc ' config_args='' hint

[perl #27530] Regex qr// interpolation fails when chr(0) is used in a thread

2004-11-18 Thread Steve Peters via RT
[rafael - Thu Mar 11 15:28:45 2004]: [EMAIL PROTECTED] wrote: The patch below (to bleadperl, but also suitable for maint) should fix it. I'm not sure where we put threads-specific tests for things like this, but the example above is pretty close to an ideal test case. Regression

[perl #32416] OK: perl v5.8.6 +RC1 on darwin-thread-multi-2level 7.6.0 (UNINSTALLED)

2004-11-12 Thread via RT
subversion 6) configuration: Platform: osname=darwin, osvers=7.6.0, archname=darwin-thread-multi-2level uname='darwin g5.local 7.6.0 darwin kernel version 7.6.0: sun oct 10 12:05:27 pdt 2004; root:xnuxnu-517.9.4.obj~1release_ppc power macintosh powerpc ' config_args='' hint

Re: [PATCH] Re: [perl #32272] Not OK: perl v5.8.5 +MAINT23414 on cygwin-thread-multi-64int 1.5.12s(0.11642) (UNINSTALLED)

2004-11-10 Thread Rafael Garcia-Suarez
Yitzchak Scott-Thoennes wrote: On Mon, Nov 01, 2004 at 07:50:30PM -, Yitzchak Scott-Thoennes wrote: t/io/tell.FAILED at test 28 The io/tell doesn't concern me; it's a questionable test, and goes away with PERLIO=perlio (or -Uusefaststdio). Here's a

Re: [PATCH] Re: [perl #32272] Not OK: perl v5.8.5 +MAINT23414 on cygwin-thread-multi-64int 1.5.12s(0.11642) (UNINSTALLED)

2004-11-10 Thread Yitzchak Scott-Thoennes
On Tue, Nov 09, 2004 at 05:40:13PM -0800, Yitzchak Scott-Thoennes [EMAIL PROTECTED] wrote: On Mon, Nov 01, 2004 at 07:50:30PM -, Yitzchak Scott-Thoennes wrote: t/io/tell.FAILED at test 28 The io/tell doesn't concern me; it's a questionable test, and goes

Re: [PATCH] Re: [perl #32272] Not OK: perl v5.8.5 +MAINT23414 on cygwin-thread-multi-64int 1.5.12s(0.11642) (UNINSTALLED)

2004-11-10 Thread Rafael Garcia-Suarez
Yitzchak Scott-Thoennes wrote: Sorry, that was not the patch I meant to send; this one actually works: OK, TODO and not SKIP, as you wish (applied as #23492.)

[PATCH] Re: [perl #32272] Not OK: perl v5.8.5 +MAINT23414 on cygwin-thread-multi-64int 1.5.12s(0.11642) (UNINSTALLED)

2004-11-09 Thread Yitzchak Scott-Thoennes
On Mon, Nov 01, 2004 at 07:50:30PM -, Yitzchak Scott-Thoennes wrote: t/io/tell.FAILED at test 28 The io/tell doesn't concern me; it's a questionable test, and goes away with PERLIO=perlio (or -Uusefaststdio). Here's a patch to skip it. It isn't actually

[perl #32272] Not OK: perl v5.8.5 +MAINT23414 on cygwin-thread-multi-64int 1.5.12s(0.11642) (UNINSTALLED)

2004-11-01 Thread via RT
: Configured by sthoenna at Mon Nov 1 02:35:07 PST 2004. Summary of my perl5 (revision 5 version 8 subversion 5 patch 23451) configuration: Platform: osname=cygwin, osvers=1.5.12s(0.11642), archname=cygwin-thread-multi-64int uname='cygwin_nt-5.1 dhx98431 1.5.12s(0.11642) 20041026 17:35:49

Re: [perl #32272] Not OK: perl v5.8.5 +MAINT23414 on cygwin-thread-multi-64int 1.5.12s(0.11642) (UNINSTALLED)

2004-11-01 Thread Nicholas Clark
Thanks for the report. Better to know about these things before a release candidate than just after. On Mon, Nov 01, 2004 at 07:50:30PM -, Yitzchak Scott-Thoennes wrote: ext/Cwd/t/cwd.readdir(linktest/..): No such file or directory at ../ext/Cwd/t/cwd.t line

Re: [perl #32272] Not OK: perl v5.8.5 +MAINT23414 on cygwin-thread-multi-64int 1.5.12s(0.11642) (UNINSTALLED)

2004-11-01 Thread Yitzchak Scott-Thoennes
On Mon, Nov 01, 2004 at 08:13:14PM +, Nicholas Clark wrote: Thanks for the report. Better to know about these things before a release candidate than just after. On Mon, Nov 01, 2004 at 07:50:30PM -, Yitzchak Scott-Thoennes wrote:

Re: [perl #32272] Not OK: perl v5.8.5 +MAINT23414 on cygwin-thread-multi-64int 1.5.12s(0.11642) (UNINSTALLED)

2004-11-01 Thread Yitzchak Scott-Thoennes
On Mon, Nov 01, 2004 at 12:27:41PM -0800, Yitzchak Scott-Thoennes wrote: On Mon, Nov 01, 2004 at 08:13:14PM +, Nicholas Clark wrote: Thanks for the report. Better to know about these things before a release candidate than just after. On Mon, Nov 01, 2004 at 07:50:30PM -, Yitzchak

Re: [perl #32272] Not OK: perl v5.8.5 +MAINT23414 on cygwin-thread-multi-64int 1.5.12s(0.11642) (UNINSTALLED)

2004-11-01 Thread Nicholas Clark
On Mon, Nov 01, 2004 at 12:31:50PM -0800, Yitzchak Scott-Thoennes wrote: On Mon, Nov 01, 2004 at 12:27:41PM -0800, Yitzchak Scott-Thoennes wrote: On Mon, Nov 01, 2004 at 08:13:14PM +, Nicholas Clark wrote: Thanks for the report. Better to know about these things before a release

Re: [perl #32272] Not OK: perl v5.8.5 +MAINT23414 on cygwin-thread-multi-64int 1.5.12s(0.11642) (UNINSTALLED)

2004-11-01 Thread H.Merijn Brand
On Mon 01 Nov 2004 20:50, Yitzchak Scott-Thoennes (via RT) [EMAIL PROTECTED] wrote: # New Ticket Created by Yitzchak Scott-Thoennes # Please include the string: [perl #32272] # in the subject line of all future correspondence about this issue. # URL:

Re: [perl #32272] Not OK: perl v5.8.5 +MAINT23414 on cygwin-thread-multi-64int 1.5.12s(0.11642) (UNINSTALLED)

2004-11-01 Thread Yitzchak Scott-Thoennes
On Mon, Nov 01, 2004 at 11:21:27PM +0100, H.Merijn Brand wrote: On Mon 01 Nov 2004 20:50, Yitzchak Scott-Thoennes wrote: ext/Cwd/t/cwd.readdir(linktest/..): No such file or directory at ../ext/Cwd/t/cwd.t line 151 # Failed test (../ext/Cwd/t/cwd.t at line

Re: [perl #32272] Not OK: perl v5.8.5 +MAINT23414 on cygwin-thread-multi-64int 1.5.12s(0.11642) (UNINSTALLED)

2004-11-01 Thread H.Merijn Brand
On Mon 01 Nov 2004 23:35, Yitzchak Scott-Thoennes [EMAIL PROTECTED] wrote: On Mon, Nov 01, 2004 at 11:21:27PM +0100, H.Merijn Brand wrote: On Mon 01 Nov 2004 20:50, Yitzchak Scott-Thoennes wrote: ext/Cwd/t/cwd.readdir(linktest/..): No such file or directory at

Re: [perl #32272] Not OK: perl v5.8.5 +MAINT23414 on cygwin-thread-multi-64int 1.5.12s(0.11642) (UNINSTALLED)

2004-11-01 Thread Yitzchak Scott-Thoennes
On Tue, Nov 02, 2004 at 01:44:46AM +0100, H.Merijn Brand wrote: On Mon 01 Nov 2004 23:35, Yitzchak Scott-Thoennes [EMAIL PROTECTED] wrote: This one went away if I symlinked cwt.t to perl_current/t Can you be more specific? On my other pc:

Re: [perl #32272] Not OK: perl v5.8.5 +MAINT23414 on cygwin-thread-multi-64int 1.5.12s(0.11642) (UNINSTALLED)

2004-11-01 Thread Yitzchak Scott-Thoennes
On Mon, Nov 01, 2004 at 08:45:33PM +, Nicholas Clark wrote: On Mon, Nov 01, 2004 at 12:31:50PM -0800, Yitzchak Scott-Thoennes wrote: Same error with perl5.8.4 and PathTools 3.01. This seems to be the same problem that Merijn found. It worked for him if he made a symllink.

Not OK: perl v5.8.5 +MAINT23414 on cygwin-thread-multi-64int 1.5.11(0.11642) (UNINSTALLED)

2004-10-26 Thread Gerrit P. Haase
Hello, To: [EMAIL PROTECTED] Subject: Not OK: perl v5.8.5 +MAINT23414 on cygwin-thread-multi-64int 1.5.11(0.11642) (UNINSTALLED) Reply-To: [EMAIL PROTECTED] Message-Id: [EMAIL PROTECTED] This is a build failure report for perl from [EMAIL PROTECTED], generated with the help of perlbug 1.35

[perl #32144] Not OK: perl v5.8.5 +MAINT23414 on cygwin-thread-multi-64int 1.5.11(0.11642) (UNINSTALLED)

2004-10-26 Thread via RT
on cygwin-thread-multi-64int 1.5.11(0.11642) (UNINSTALLED) Reply-To: [EMAIL PROTECTED] Message-Id: [EMAIL PROTECTED] This is a build failure report for perl from [EMAIL PROTECTED], generated with the help of perlbug 1.35 running under perl v5.8.5

[perl #32074] Thread Synchronization issues

2004-10-21 Thread via RT
these: -- #!/usr/bin/perl use Thread; use Thread::Queue; $queue = Thread::Queue-new(); $producer = Thread-new(\produce, $queue); $consumer = Thread-new(\consume, $queue); $producer-join(); $consumer-join(); sub produce { my ($queue) = @_; foreach $i (1..10) { $queue

Re: [perl #32074] Thread Synchronization issues

2004-10-21 Thread Elizabeth Mattijsen
and 5.8.5, I had problems with Scripts like these: -- #!/usr/bin/perl use Thread; Why use Thread? Please do a perldoc Thread and see that it says: For new code the use of the Thread module is discouraged and the direct use of the threads and threads::shared modules

[perl #30062] Windows/Win32 thread handle leak with threads join

2004-06-06 Thread via RT
with sysinternals Handle utility, available at: http://www.sysinternals.com/ntw2k/freeware/handle.shtml indicates there are about 1000 open Win32 thread handles at the time of the sleep(60) below. (You can also check the open handle count via Windows Task Manager or other tool). ---snip

Re: Are perl_parse and perl_run thread safe?

2004-02-08 Thread Nick Ing-Simmons
Aditya Prasad [EMAIL PROTECTED] writes: Hello, I wanted to know if the functions perl_parse and perl_run are thread safe. In other words, i am using multiple perl interpreters allocated in different threads and these threads will be running parallely. I noticed that when one of the threads

Re: 5.8.3 RC1 (Thread::Bless)

2004-01-08 Thread Elizabeth Mattijsen
present with 5.8.2? Indeed. Although 5.8.2 had its own share of problems. This is the test output under 5.8.2: all tests are successful, but there is a lot of noise: $ perl5.8.2-threaded Makefile.PL Writing Makefile for Thread::Bless $ make test PERL_DL_NONLAZY=1 /usr/local/bin/perl5.8.2-threaded

Re: Not OK: perl v5.8.1 +RC4 on i386-linux-thread-multi 2.4.18-686

2003-09-11 Thread Andy Dougherty
This is a build failure report for perl from [EMAIL PROTECTED], generated with the help of perlbug 1.34 running under perl v5.8.1. I just built perl-5.8.1-RC4 on my Debian GNU/Linux system and failed one test in an extention module: ExtUtils/t/Embed. Since I believe that 5.8.1 is due to be

Thread fails in 18417

2003-01-06 Thread H.Merijn Brand
As of 18417 I see thread failures on *all* my systems. 18358 was still a full OK. Changelog 18358..18451 on the bottom. That's beyond 18417 because I saw some thread changes past 18417 Automated smoke report for patch 18417 ccgcc

Re: Thread fails in 18417

2003-01-06 Thread H.Merijn Brand
On Mon 06 Jan 2003 09:11, H.Merijn Brand [EMAIL PROTECTED] wrote: As of 18417 I see thread failures on *all* my systems. 18358 was still a full OK. Changelog 18358..18451 on the bottom. That's beyond 18417 because I saw some thread changes past 18417 FWIW .. worsened the case ext/DB_File/t/db

Re: [Memory] thread equality

2002-09-26 Thread Elizabeth Mattijsen
object, within the same thread of course. And the odd thing is that it is not that difficult in threads to do: a package lexical (inside threads.pm) would do the trick. The CLONE subroutine should reset it and the -self method would set it if it was not set yet. Something like my $self; sub

[FYI] Thread::Status

2002-09-17 Thread Elizabeth Mattijsen
The uploaded file Thread-Status-0.02.tar.gz has entered CPAN as file: $CPAN/authors/id/E/EL/ELIZABETH/Thread-Status-0.02.tar.gz size: 9683 bytes md5: 3f996aa837a1a560913a635bab5093b0 =head1 NAME Thread::Status - report stack status of all running threads =head1 SYNOPSIS

[perl #17057] POSIX::_exit within thread on Linux

2002-09-06 Thread via RT
. Inspection with top reveals that this is probably caused by the fact that the process for the thread exits without letting anybody else know it left. perl -Mthreads -MPOSIX -e 'threads-new( sub { 1 while 1 } )-join' shows three processes under Linux, whereas the POSIX::_exit() version shows only

Re: Killing a thread without die()

2002-09-02 Thread Nick Ing-Simmons
Bart Schuller [EMAIL PROTECTED] writes: At 2:21 PM +0200 9/2/02, Elizabeth Mattijsen wrote: Is there a way to let a thread stop without using die()? Other than return() from the top level of the thread, of course. Or is there a way If the preferred way of exiting a thread *is* a return from

Re: Killing a thread without die()

2002-09-02 Thread Nick Ing-Simmons
Dan Sugalski [EMAIL PROTECTED] writes: At 4:57 PM +0200 9/2/02, Elizabeth Mattijsen wrote: At 10:14 AM 9/2/02 -0400, Dan Sugalski wrote: At 2:21 PM +0200 9/2/02, Elizabeth Mattijsen wrote: Is there a way to let a thread stop without using die()? Other than return() from the top level

Re: $$ of thread?

2002-08-02 Thread Rafael Garcia-Suarez
Tony Cook wrote: On Thu, 1 Aug 2002, Rafael Garcia-Suarez wrote: Elizabeth Mattijsen wrote: Is it possible to get at the process number of the process handling a thread? POSIX::getpid should work, am I correct ? POSIX::getpid() just returns $$ That's right, I should have looked

Re: $$ of thread?

2002-08-02 Thread Elizabeth Mattijsen
not asking to have $$ change it's current behaviour. If you want to kill a Perl threaded application, killing one $$ value should be enough. It's just that for this scheduling priority thing, at least under Linux, it would be nice if there would be _another_ way to get at the pid of the thread

RE: Thread::Use - use a module inside a thread only

2002-07-31 Thread Green, Paul
Maybe an I/O layer should be required to explicitly declare itself thread-safe? (Or whatever thread-xxx term I mean here). Any layer not declared thread-safe should be removed when a new thread is created. (And now perl can print a warning, since it is doing something you might not like might

Re: [PATCH] Thread::Queue-dequeue_keep

2002-07-25 Thread Elizabeth Mattijsen
At 04:06 PM 7/26/02 -0400, Sam Tregar wrote: On Thu, 25 Jul 2002, Elizabeth Mattijsen wrote: Agree, but if you are sure you're the only one left (e.g. after all of the other threads have been join()ed), you can use this to see if there is anything left in the queue without disturbing it...

[ID 20020715.002] Not OK: perl v5.8.0 on MSWin32-x86-multi-thread 4.0 (UNINSTALLED)

2002-07-15 Thread Andreas Fehr
=install severity=none --- Site configuration information for perl v5.8.0: Configured by FehrA at Mon Jul 15 08:26:52 2002. Summary of my perl5 (revision 5 version 8 subversion 0) configuration: Platform: osname=MSWin32, osvers=4.0, archname=MSWin32-x86-multi-thread uname='' config_args

Re: CPAN Upload: E/EL/ELIZABETH/Thread-Pool-0.03.tar.gz

2002-07-14 Thread Elizabeth Mattijsen
At 02:44 PM 7/14/02 +0200, Arthur Bergman wrote: You are trusting thread inertia! Bad programmer no cookie ;-). ok, found your article on Perl.com... reading it now... Liz

Re: [ID 20020602.007] strange timing dependent thread events

2002-06-08 Thread Jarkko Hietaniemi
Ok, I think that patch17080 solved this problem could you please try again and confirm it? FWIW I run the test snippet in a multi-CPU alpha a few dozen times and did not see the scary error message (only the A thread exited while). Arthur -- $jhi++; # http://www.iki.fi/jhi

Re: [ID 20020602.007] strange timing dependent thread events

2002-06-08 Thread Elizabeth Mattijsen
At 01:07 PM 6/8/02 +0200, Arthur Bergman wrote: = use threads; threads-new( \sub1 ); sub sub1 { print Now in thread\n; threads-self-detach; } = About one in three times

Re: [ID 20020602.007] strange timing dependent thread events

2002-06-03 Thread Arthur Bergman
On måndag, juni 3, 2002, at 10:16 , Elizabeth Mattijsen wrote: At 09:57 AM 6/3/02 +0200, Arthur Bergman wrote: Well, the thread should have finished after the detach. I guess I'm still thinking too linear in this respect and not parallel enough... ;-) No, actually the thread is running

[ID 20020530.001] Not OK: perl v5.8.0 +DEVEL16859 on MSWin32-x86-multi-thread 4.0 (UNINSTALLED)

2002-05-30 Thread Andreas Fehr
information for perl v5.8.0: Configured by FehrA at Thu May 30 14:49:28 2002. Summary of my perl5 (revision 5 version 8 subversion 0) configuration: Platform: osname=MSWin32, osvers=4.0, archname=MSWin32-x86-multi-thread uname='' config_args='undef' hint=recommended, useposix=true

Re: [ID 20020328.001] Not OK: perl v5.7.3 +DEVEL15550 on MSWin32-x86-multi-thread 4.0 (UNINSTALLED)

2002-04-04 Thread Michael G Schwern
On Thu, Apr 04, 2002 at 11:55:10PM +0200, Mattia Barbon wrote: ok 13 Microsoft (R) Program Maintenance Utility Version 1.62.7022 Copyright (C) Microsoft Corp 1988-1997. All rights reserved. NMAKE : fatal error U1073: don't know how to make 'C:\Developement\perl5\perl-

Re: [ID 20010909.026] Not OK: perl v5.7.2 +DEVEL11937 on MSWin32-x86-multi-thread 4.0 (UNINSTALLED)

2001-09-10 Thread John Peacock
Andreas Fehr wrote: Strange, cause all 'released'-versions I have are 100% OK (5.6.1, 5.7.1, 5.7.2). So there might be people with other ideas of whether tests have to pass or not. One of the usual ways to fix test errors under Win32 is to route around it (i.e. skip for that platform).

Re: [ID 20010909.026] Not OK: perl v5.7.2 +DEVEL11937 on MSWin32-x86-multi-thread 4.0 (UNINSTALLED)

2001-09-10 Thread John Peacock
Andreas Fehr wrote: Strange, cause all 'released'-versions I have are 100% OK (5.6.1, 5.7.1, 5.7.2). So there might be people with other ideas of whether tests have to pass or not. One of the usual ways to fix test errors under Win32 is to route around it (i.e. skip for that platform).

Re: [ID 20010626.001] Not OK: perl v5.7.1 +DEVEL10929 onMSWin32-x86-multi-thread 4.0 (UNINSTALLED)

2001-06-26 Thread Andreas Fehr
On 2001-06-26, 15:57, H.Merijn Brand wrote: HB On Tue 26 Jun 2001 15:24, Andreas Fehr [EMAIL PROTECTED] wrote: HB On 2001-06-26, 08:09, Jarkko Hietaniemi wrote: HB HB JH I didn't find any reference in the README, how to configure libnet so it HB JH doesn't complain about the configuration:

Re: [ID 20010530.004] Not OK: perl v5.7.1 +DEVEL10326 on MSWin32-x86-multi-thread 4.0 (UNINSTALLED)

2001-05-31 Thread Nick Ing-Simmons
Andreas Fehr [EMAIL PROTECTED] writes: Failed Test Stat Wstat Total Fail Failed List of Failed --- lib/extutils.t 101 10.00% 10 With my copy that is now only fail with Mingw32. It is due to

Thread safe regex engine?

2001-05-18 Thread Artur Bergman
Hi, I have understood that the current ithread implmentation is unsafe because of the regex engine. The only notes I could find on this is ActiveStates release notes on the pseudo forking. My very limited understand of the issue is that the regex engine changes the op tree for certain cases

  1   2   >