Project

General

Profile

Activity

From 02/05/2010 to 02/11/2010

02/11/2010

01:50 AM Backport #2728: ruby segfaults returning from dynamically defined method in ensure block
=begin
r26628 caused new SEGV when executing rubyspec.
Though the detail is still under investigation, I temporari...
mame (Yusuke Endoh)

02/10/2010

05:18 AM Backport #2726: udp socket send and receive leak handles on windows
=begin
appears fixed in ruby 1.9.2dev (2010-02-08 trunk 26621) [i386-mingw32]

Also your snippet requires Socket...
rogerdpack (Roger Pack)
05:10 AM Bug #2714: Interpreter deadlock when using ::Socket.pair
=begin
seemed to work ok for me with cygwin 1.8.7 (if that's helpful)
=end
rogerdpack (Roger Pack)
04:45 AM Backport #2728 (Assigned): ruby segfaults returning from dynamically defined method in ensure block
=begin

=end
nobu (Nobuyoshi Nakada)
04:44 AM Backport #2728 (Closed): ruby segfaults returning from dynamically defined method in ensure block
=begin
Fixed in r26628.
=end
nobu (Nobuyoshi Nakada)
03:58 AM Backport #2728: ruby segfaults returning from dynamically defined method in ensure block
=begin
It is reproducing on ruby 1.9.1p243 Mac OS X 1.6
=end
kronos (Ivan Samsonov)
01:26 AM Backport #2728 (Closed): ruby segfaults returning from dynamically defined method in ensure block
=begin
As best as I can work out, the conditions to reproduce this crash are:
1. A begin/ensure block yields to a...
Ethan (Ethan -)

02/09/2010

11:58 PM Bug #2727 (Third Party's Issue): make: *** [encdb.h] Aborted
=begin
Ubuntu 9.10 の環境で ruby_1_9_1 を make すると encdb.h のところでアボートします。
gcc version 4.4.1 (Ubuntu 4.4.1-4ubuntu9) なので ...
znz (Kazuhiro NISHIYAMA)
04:44 AM Backport #2726 (Closed): udp socket send and receive leak handles on windows
=begin
UDP receiver:
require 'socket'

dis_socket = Socket.new( Socket::AF_INET, Socket::SOCK_DGRAM, 0 )
di...
ironfe56 (John Stewart)

02/08/2010

09:18 AM Bug #2670: Net::IMAP parser problem
=begin
I've reproduced this in ruby 1.8.7 (2008-08-11 patchlevel 72) [universal-darwin10.0], and a user reports that...
rgrove (Ryan Grove)
06:26 AM Feature #2720: Segfault during multiple calls to C embedded Ruby wrapped with dl library
=begin
Well, I idenfitied that this bug is due to an unexpected behavior with dlclose().

My question is : why r...
marchaland (David MARCHALAND)
01:33 AM Feature #2720 (Rejected): Segfault during multiple calls to C embedded Ruby wrapped with dl library
=begin
Hi Ruby developpers,

I embedded a Ruby interpreter into a C application through a shared library. This a...
marchaland (David MARCHALAND)

02/07/2010

08:28 AM Bug #2670: Net::IMAP parser problem
=begin
I've tested this with "ruby 1.9.2dev (2010-02-03 trunk 26544) [x86_64-linux]" and it seems to be working now;...
mithrandi (Tristan Seligmann)
03:52 AM Bug #2718 (Assigned): DRb mixing up function return values between PIDs after fork()
=begin
The precise details are in the attached test case, but the basic version goes as such: Child pid 1 calls meth...
rhythmx (Sean Bradly)
01:36 AM Bug #2714 (Assigned): Interpreter deadlock when using ::Socket.pair
=begin

=end
naruse (Yui NARUSE)

02/06/2010

11:12 PM Bug #2670: Net::IMAP parser problem
=begin
It seems that the bug has already been fixed in svn trunk.
Could you try svn trunk?
=end
shugo (Shugo Maeda)
04:31 AM Bug #2714: Interpreter deadlock when using ::Socket.pair
=begin
Narrowed this issue down to the cygwin build.

Works correctly on the following:
* ruby 1.8.7 (2008...
sf (s f)
03:44 AM Bug #2714: Interpreter deadlock when using ::Socket.pair
=begin
with mingw, I get

c:\dev_old\digitalarchive_trunk>ruby -v bad.rb
ruby 1.9.1p376 (2009-12-07 revision 2...
rogerdpack (Roger Pack)
12:43 AM Bug #2714 (Assigned): Interpreter deadlock when using ::Socket.pair
=begin
Hello,

I have come across a deadlock situation (of the entire ruby interpreter) when using ::Socket.pair...
sf (s f)
03:41 AM Bug #1820 (Open): Always spawns a thread that loops on the futex syscall
=begin
ahh it appears to also wake up once every 10ms in linux.
Anybody know if this is avoidable by using pause()...
rogerdpack (Roger Pack)

02/05/2010

06:49 PM Bug #1820: Always spawns a thread that loops on the futex syscall
=begin
It is not using 100% of one core, not at all. But it causes frequent wakeups that prevent the CPU from going ...
mxey (Maximilian Gass)
05:30 AM Bug #1820: Always spawns a thread that loops on the futex syscall
=begin
Is it using 100% of one core?

With my irb (ubuntu), 1.9.1p376 here's my strace without entering the key ...
rogerdpack (Roger Pack)
 

Also available in: Atom