Debian Bug report logs - #472702
ruby1.8: thread implementation has "a couple serious bugs"

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Matt Zagrabelny <mzagrabe@d.umn.edu>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: ruby1.8: thread implementation has "a couple serious bugs"

Date: Tue, 25 Mar 2008 16:12:54 -0500

Package: ruby1.8
Version: 1.8.6.114-2
Severity: normal


According to a discussion thread on Google's ruby-talk [1], there are "a
couple serious bugs" in Ruby's thread implementation.

Please consider rebuilding the package using the thread.c file found at
[2].

If this fix is done, then there will be no need to package
libfastthread-ruby and bug #472500 can be closed.

[1] http://groups.google.com/group/ruby-talk-google/browse_thread/thread/7933e7e987dad1c3
[2] http://svn.ruby-lang.org/cgi-bin/viewvc.cgi/branches/ruby_1_8/ext/thread/thread.c?revision=12278

Thanks,


-- System Information:
Debian Release: lenny/sid
  APT prefers unstable
  APT policy: (990, 'unstable'), (500, 'testing'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.24-1-686 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages ruby1.8 depends on:
ii  libc6                        2.7-9       GNU C Library: Shared libraries
ii  libruby1.8                   1.8.6.114-2 Libraries necessary to run Ruby 1.

ruby1.8 recommends no packages.

-- no debconf information

Message #10 received at 472702@bugs.debian.org (full text, mbox, reply):

From: Lucas Nussbaum <lucas@lucas-nussbaum.net>

To: Matt Zagrabelny <mzagrabe@d.umn.edu>, 472702@bugs.debian.org

Cc: Debian Bug Tracking System <control@bugs.debian.org>, pkg-ruby-extras@lists.alioth.debian.org, 472500@bugs.debian.org

Subject: Re: Bug#472702: ruby1.8: thread implementation has "a couple serious bugs"

Date: Wed, 26 Mar 2008 00:12:35 +0100

tags 472702 + moreinfo unreproducible
thanks

On 25/03/08 at 16:12 -0500, Matt Zagrabelny wrote:
> Package: ruby1.8
> Version: 1.8.6.114-2
> Severity: normal
> 
> 
> According to a discussion thread on Google's ruby-talk [1], there are "a
> couple serious bugs" in Ruby's thread implementation.

Please provide precise pointers to the bugs (or code to reproduce them).
The mailing list thread you are pointing to is very old, and only
contains vague accusations.

> Please consider rebuilding the package using the thread.c file found at
> [2].

This version is older than the one in the package. So no.

> If this fix is done, then there will be no need to package
> libfastthread-ruby and bug #472500 can be closed.
> 
> [1] http://groups.google.com/group/ruby-talk-google/browse_thread/thread/7933e7e987dad1c3
> [2] http://svn.ruby-lang.org/cgi-bin/viewvc.cgi/branches/ruby_1_8/ext/thread/thread.c?revision=12278
-- 
| Lucas Nussbaum
| lucas@lucas-nussbaum.net   http://www.lucas-nussbaum.net/ |
| jabber: lucas@nussbaum.fr             GPG: 1024D/023B3F4F |

Message #17 received at 472702@bugs.debian.org (full text, mbox, reply):

From: akira yamada <akira@debian.org>

To: Lucas Nussbaum <lucas@lucas-nussbaum.net>, 472702@bugs.debian.org

Cc: Matt Zagrabelny <mzagrabe@d.umn.edu>, pkg-ruby-extras@lists.alioth.debian.org, 472500@bugs.debian.org

Subject: Re: Bug#472702: ruby1.8: thread implementation has "a couple serious bugs"

Date: Wed, 26 Mar 2008 19:40:10 +0900

Hi,

>> According to a discussion thread on Google's ruby-talk [1], there are "a
>> couple serious bugs" in Ruby's thread implementation.
> 
> Please provide precise pointers to the bugs (or code to reproduce them).
> The mailing list thread you are pointing to is very old, and only
> contains vague accusations.

I don't know detail of the problem.
But Capistrano 2.1 print outs the following message:

  You are running Ruby 1.8.6, which has a bug in its threading implementation.
  You are liable to encounter deadlocks running Capistrano, unless you install
  the fastthread library, which is available as a gem:

I think that it is a case of "a couple serious bugs".
(I couldn't find detail of the reason of
the message from the svn-repo of Capistrano.)

I tested about this message using unit-tests of Capistrano 2.1.

When I run the tests with ruby1.8_1.8.6-2,
the result was the following:

  $ rake
  [...]
  Loaded suite /usr/lib/ruby/1.8/rake/rake_test_loader
  Started
  ... [...] ...deadlock 0xb76afb14: sleep:-  - ./test/../lib/capistrano/gateway.rb:57
  deadlock 0xb7c3a700: sleep:- (main) - ./test/../lib/capistrano/gateway.rb:64
  ./test/../lib/capistrano/gateway.rb:64:in `wait': Thread(0xb7c3a700): deadlock (fatal)

And when I run it with ruby1.8_1.8.6.36-1 or ruby1.8_1.8.6.111-2,
the result was all OK.

-- 
ay

Message #22 received at 472702@bugs.debian.org (full text, mbox, reply):

From: Matt Zagrabelny <mzagrabe@d.umn.edu>

To: akira yamada <akira@debian.org>

Cc: Lucas Nussbaum <lucas@lucas-nussbaum.net>, 472702@bugs.debian.org, pkg-ruby-extras@lists.alioth.debian.org, 472500@bugs.debian.org

Subject: Re: Bug#472702: ruby1.8: thread implementation has "a couple serious bugs"

Date: Wed, 26 Mar 2008 09:14:34 -0500

[Message part 1 (text/plain, inline)]

Hi,

> I don't know detail of the problem.

Unfortunately neither do I. I was taking Capistrano and the ruby-talk
thread's "word" that there was a problem.

> But Capistrano 2.1 print outs the following message:
> 
>   You are running Ruby 1.8.6, which has a bug in its threading implementation.
>   You are liable to encounter deadlocks running Capistrano, unless you install
>   the fastthread library, which is available as a gem:
> 
> I think that it is a case of "a couple serious bugs".
> (I couldn't find detail of the reason of
> the message from the svn-repo of Capistrano.)
> 
> I tested about this message using unit-tests of Capistrano 2.1.
> 
> When I run the tests with ruby1.8_1.8.6-2,
> the result was the following:
> 
>   $ rake
>   [...]
>   Loaded suite /usr/lib/ruby/1.8/rake/rake_test_loader
>   Started
>   ... [...] ...deadlock 0xb76afb14: sleep:-  - ./test/../lib/capistrano/gateway.rb:57
>   deadlock 0xb7c3a700: sleep:- (main) - ./test/../lib/capistrano/gateway.rb:64
>   ./test/../lib/capistrano/gateway.rb:64:in `wait': Thread(0xb7c3a700): deadlock (fatal)
> 
> And when I run it with ruby1.8_1.8.6.36-1 or ruby1.8_1.8.6.111-2,
> the result was all OK.

So the current version of ruby1.8 looks good. I will close the bug.
Thanks for your time.

Whoever packages Capistrano for Debian should then disable the warning
about fastthread, since it is fixed in ruby1.8.

-- 
Matt Zagrabelny - mzagrabe@d.umn.edu - (218) 726 8844
University of Minnesota Duluth
Information Technology Systems & Services
PGP key 1024D/84E22DA2 2005-11-07
Fingerprint: 78F9 18B3 EF58 56F5 FC85  C5CA 53E7 887F 84E2 2DA2

He is not a fool who gives up what he cannot keep to gain what he cannot
lose.
-Jim Elliot

[signature.asc (application/pgp-signature, inline)]

Message #27 received at 472702-done@bugs.debian.org (full text, mbox, reply):

From: Matt Zagrabelny <mzagrabe@d.umn.edu>

To: 472702-done@bugs.debian.org

Subject: already fixed

Date: Wed, 26 Mar 2008 09:21:34 -0500

[Message part 1 (text/plain, inline)]

Bug was already fixed in Debian archive.

-- 
Matt Zagrabelny - mzagrabe@d.umn.edu - (218) 726 8844
University of Minnesota Duluth
Information Technology Systems & Services
PGP key 1024D/84E22DA2 2005-11-07
Fingerprint: 78F9 18B3 EF58 56F5 FC85  C5CA 53E7 887F 84E2 2DA2

He is not a fool who gives up what he cannot keep to gain what he cannot
lose.
-Jim Elliot

[signature.asc (application/pgp-signature, inline)]

Message #32 received at 472702@bugs.debian.org (full text, mbox, reply):

From: Daigo Moriwaki <beatles@sgtpepper.net>

To: Matt Zagrabelny <mzagrabe@d.umn.edu>, 472702@bugs.debian.org

Cc: akira yamada <akira@debian.org>, Lucas Nussbaum <lucas@lucas-nussbaum.net>, pkg-ruby-extras@lists.alioth.debian.org, 472500@bugs.debian.org

Subject: Re: Bug#472702: ruby1.8: thread implementation has "a couple serious bugs"

Date: Wed, 26 Mar 2008 23:58:12 +0900

Hi Matt,

Matt Zagrabelny wrote:
>> I don't know detail of the problem.
> 
> Unfortunately neither do I. I was taking Capistrano and the ruby-talk
> thread's "word" that there was a problem.

I asked ruby-dev and Nakada-san replied.
He said that Ruby 1.8.6 p110 was merged (backport) with fastthread, and that the 
current situation is opposite. fastthread 1.0.1 does not yet fix an issue that 
Ruby 1.8.6 p110 has fixed. You should not use fastthread 1.0.1 with Ruby 1.8.6 
p110 or later. So, you don't have to care about fastthread. Use Debian's latest 
Ruby package.

Sorry, I don't know what the issue is, though.


Regards,
Daigo

-- 
Daigo Moriwaki
beatles at sgtpepper dot net

Send a report that this bug log contains spam.