Project

General

Profile

Activity

From 01/24/2010 to 01/30/2010

01/30/2010

11:12 PM Bug #2692: Ruby hangs after returning from rescue clause inside the block
=begin
Hi Ilya --

2010/1/30 Ilya Lopatkin <redmine@ruby-lang.org>:
> def foo
> some_block = -> do
> 0...
mame (Yusuke Endoh)
06:54 PM Bug #2692 (Closed): Ruby hangs after returning from rescue clause inside the block
=begin
Here is the sample code:
def foo
some_block = -> do
0.upto(1000) do |i|
begin
r...
Uriel (Ilya Lopatkin)
10:22 PM Backport #2473: Handle leak in TCPServer on Windows
=begin
I did not merge r24218 into ruby_1_9_1, so r25569 is not applicable.

Is the reported problem still repro...
yugui (Yuki Sonoda)
10:02 PM Backport #1913 (Closed): in `write': Not enough space - <STDOUT> (Errno::ENOMEM) on Windows XP
=begin

=end
yugui (Yuki Sonoda)
09:57 PM Backport #1072 (Closed): Ripper#filename
=begin
This issue was solved with changeset r26508.
Kazuhiro, thank you for reporting this issue.
Your contributio...
yugui (Yuki Sonoda)
10:15 AM Bug #1560 (Rejected): multi core operations are slower on trunk (possible regression)
=begin

=end
nobu (Nobuyoshi Nakada)

01/29/2010

11:51 PM Bug #1560: multi core operations are slower on trunk (possible regression)
=begin
Hi,

In message "Re: [ruby-core:27872] [Bug #1560] multi core operations are slower on trunk (possible regr...
matz (Yukihiro Matsumoto)
10:52 AM Bug #2682 (Feedback): Undefined method join for String (erb.rb)
=begin
Can't reproduce on Ruby 1.9.
Please copy & paste exact ruby -v string.
=end
naruse (Yui NARUSE)
02:57 AM Bug #2682 (Closed): Undefined method join for String (erb.rb)
=begin
Error when running gem bundle command

Exception `NoMethodError' at c:/ruby19/lib/ruby/1.9.1/erb.rb:753 -...
awkwood (awk wood)

01/28/2010

06:51 PM Backport #2564: [patch] re-initialize timer_thread_{lock,cond} after fork
=begin
Indeed. I was wrong. But there's still bug in 1.9.1. native_stop_timer_thread() doesn't wait till timer threa...
alk (Aliaksey Kandratsenka)
03:32 PM Backport #2564: [patch] re-initialize timer_thread_{lock,cond} after fork
=begin
My understanding is following:

a) lets suppose timer thread is doing some periodic work. This means that...
naruse (Yui NARUSE)
06:25 PM Bug #2670: Net::IMAP parser problem
=begin

=end
shugo (Shugo Maeda)
08:39 AM Bug #2670 (Closed): Net::IMAP parser problem
=begin
Using Net::IMAP against Dovecot (1.2.10) results in problems when switching between folders:

C: RUBY0003...
mithrandi (Tristan Seligmann)
11:15 AM Backport #2672 (Open): backport 26395
=begin
If you get a chance to...

ref:
http://redmine.ruby-lang.org/issues/show/2610

This would allow rub...
rogerdpack (Roger Pack)

01/27/2010

11:47 PM Backport #2564: [patch] re-initialize timer_thread_{lock,cond} after fork
=begin
It seems I'm not stating the problem clearly enough.

What happens:
a) lets suppose timer thread is doing ...
alk (Aliaksey Kandratsenka)
08:27 PM Backport #2564: [patch] re-initialize timer_thread_{lock,cond} after fork
=begin
Hi Aliaksey,

native_stop_timer_thread() sleep until timer thread die by pthread_join().

If your pat...
kosaki (Motohiro KOSAKI)
07:30 AM Backport #2564: [patch] re-initialize timer_thread_{lock,cond} after fork
=begin
No. http://redmine.ruby-lang.org/issues/show/2394 is unrelated.
=end
alk (Aliaksey Kandratsenka)
07:28 AM Backport #2564: [patch] re-initialize timer_thread_{lock,cond} after fork
=begin
Yes I can. But I'd like to avoid doing that. Reliable reproduction of such tiny races is not trivial. I have ...
alk (Aliaksey Kandratsenka)
04:57 AM Backport #2564: [patch] re-initialize timer_thread_{lock,cond} after fork
=begin
I know there was some change to mutexes recently:

http://redmine.ruby-lang.org/issues/show/2394

did...
rogerdpack (Roger Pack)
06:46 PM Bug #2201: Process.spawn fails in 1.9.1
=begin
Hi,

In message "Re: [ruby-core:27856] [Bug #2201] Process.spawn fails in 1.9.1"
on Wed, 27 Jan 2010 0...
matz (Yukihiro Matsumoto)
09:54 AM Bug #2201 (Closed): Process.spawn fails in 1.9.1
=begin

=end
rogerdpack (Roger Pack)
04:55 AM Bug #2201: Process.spawn fails in 1.9.1
=begin
appears this has been fixed in p376, if somebody wants to close the ticket (or make me a contributor to the 1...
rogerdpack (Roger Pack)
04:42 PM Bug #2638: ruby-1.9.1-p37[68] build on aix5.3 with gcc-4.2 failed to run for me because it ignores where libgcc is located.
=begin
Hello Sir,

Just a small update to tell you how did I also manage some 'make test'.

Because ruby1.9 ...
rubisher (Joel Soete)
10:00 AM Bug #1544: rb_io_write bug?
=begin
Can you extract a small reproducible script?
-r
=end
rogerdpack (Roger Pack)
09:55 AM Backport #1569: gem update --system crashes ruby with a segmentation fault.
=begin
Do you get this problem with newer versions of 1.9.1?
=end
rogerdpack (Roger Pack)
09:53 AM Bug #2358: Segmentation fault using dl/import
=begin
could you give us the gdb backtrace? (suspected bug in the extension...)
=end
rogerdpack (Roger Pack)
09:52 AM Bug #1820 (Rejected): Always spawns a thread that loops on the futex syscall
=begin
I think this is expected since it spawn one thread to just handle incoming signals. If it's not then please ...
rogerdpack (Roger Pack)
09:51 AM Backport #1940: Segmentation fault on TestFiber#test_many_fibers_with_threads (make check)
=begin
Luis do you get these with the latest trunk (1.9.2)?
=end
rogerdpack (Roger Pack)
09:50 AM Backport #1567: socket.c silently discards internal listen(2) failures
=begin
was this updated in trunk? if so which revision?
=end
rogerdpack (Roger Pack)
09:49 AM Bug #1560: multi core operations are slower on trunk (possible regression)
=begin
interesting.

for me it's

ruby 1.9.1p376 (2009-12-07 revision 26041) [i386-mingw32]
Total number...
rogerdpack (Roger Pack)
09:42 AM Bug #2303 (Third Party's Issue): dl.so segfaults on mingw32
=begin
appears to be unavoidable for Windows Server 2008.
=end
rogerdpack (Roger Pack)
09:42 AM Backport #2399: pthread_mutex_lock: 22
=begin
do you get this with trunk?
=end
rogerdpack (Roger Pack)

01/26/2010

06:05 PM Bug #2638: ruby-1.9.1-p37[68] build on aix5.3 with gcc-4.2 failed to run for me because it ignores where libgcc is located.
=begin
Hello Sir,

Please accept my apology, I am always trying to be more accurate in my pr report but here I w...
rubisher (Joel Soete)
01:22 AM Bug #2638: ruby-1.9.1-p37[68] build on aix5.3 with gcc-4.2 failed to run for me because it ignores where libgcc is located.
=begin
Sorry, it seemed that my issue seemed to be different from yours.
In my env, the file which ruby can not fin...
kanemoto (Yutaka Kanemoto)
01:13 AM Bug #2638: ruby-1.9.1-p37[68] build on aix5.3 with gcc-4.2 failed to run for me because it ignores where libgcc is located.
=begin
Hello Joel,

Are you using --enable-shared when you run configure?
If so, is it possible to try without --...
kanemoto (Yutaka Kanemoto)
04:51 PM Backport #2564: [patch] re-initialize timer_thread_{lock,cond} after fork
=begin
Can you make minimum reproducing program?
It can be either minumum C code for specific environment or Ruby ...
naruse (Yui NARUSE)
04:01 PM Backport #2564: [patch] re-initialize timer_thread_{lock,cond} after fork
=begin
Do you need some further comments or help ? I'd like to get this verified/applied, 'cause it seems quite triv...
alk (Aliaksey Kandratsenka)
06:20 AM Backport #2654 (Assigned): segfault on self thread join
=begin
thread.c of r26390 without the first hunk.
=end
nobu (Nobuyoshi Nakada)
02:32 AM Backport #2654 (Assigned): segfault on self thread join
=begin
for me, this code

Thread.new { sleep 0.1 }
Thread.list.each{|t| t.join}

seg faults on mingw 1.9.1...
rogerdpack (Roger Pack)

01/25/2010

10:51 PM Bug #2638: ruby-1.9.1-p37[68] build on aix5.3 with gcc-4.2 failed to run for me because it ignores where libgcc is located.
=begin
I see, please report it when you can.
=end
naruse (Yui NARUSE)
10:42 PM Bug #2638: ruby-1.9.1-p37[68] build on aix5.3 with gcc-4.2 failed to run for me because it ignores where libgcc is located.
=begin
Sorry Sir to disappoint you, first because I don't have direct access to svn ruby trunk (and I would very nee...
rubisher (Joel Soete)
05:34 PM Bug #2638: ruby-1.9.1-p37[68] build on aix5.3 with gcc-4.2 failed to run for me because it ignores where libgcc is located.
=begin
1.9.1's configure --help doesn't have description about --with-opt-dir (r25767) but it actually has option.
...
naruse (Yui NARUSE)
05:17 PM Bug #2638: ruby-1.9.1-p37[68] build on aix5.3 with gcc-4.2 failed to run for me because it ignores where libgcc is located.
=begin
no luck to me:
root@myserver:/.../ruby-1.9.1-p378-aix0 # ./configure --help
`configure' configures this p...
rubisher (Joel Soete)
11:01 AM Bug #2638 (Assigned): ruby-1.9.1-p37[68] build on aix5.3 with gcc-4.2 failed to run for me because it ignores where libgcc is located.
=begin

=end
yugui (Yuki Sonoda)
09:54 AM Bug #2638: ruby-1.9.1-p37[68] build on aix5.3 with gcc-4.2 failed to run for me because it ignores where libgcc is located.
=begin
./configure --with-opt-dir=/opt/mce-pware can help you?

% ./configure --help
`configure' configures ...
naruse (Yui NARUSE)
10:05 AM Backport #2609 (Assigned): threaded tests fail in 1.9.1 on OS X 10.5
=begin
They are considered as the problem of tests, and they are fixed in trunk:
* r24232 for test_io.rb
* r2485...
naruse (Yui NARUSE)
09:57 AM Backport #2633 (Assigned): warning
=begin
r23483
=end
naruse (Yui NARUSE)

01/24/2010

09:39 PM Bug #2638 (Assigned): ruby-1.9.1-p37[68] build on aix5.3 with gcc-4.2 failed to run for me because it ignores where libgcc is located.
=begin
Hello all,

This issue is very tricky, though.

For my build, I am using tools of "AIX Toolbox for Li...
rubisher (Joel Soete)
 

Also available in: Atom