[#30995] [Bug #3523] win32 exception c0000029 on exit using fibers — B Kelly <redmine@...>

Bug #3523: win32 exception c0000029 on exit using fibers

19 messages 2010/07/02

[#31100] [rubysoc] Queue C-extension patch to come — Ricardo Panaggio <panaggio.ricardo@...>

Hello,

26 messages 2010/07/07
[#31148] Re: [rubysoc] Queue C-extension patch to come — Roger Pack <rogerdpack2@...> 2010/07/09

> As this it my first patch to Ruby, I don't know where to begin with.

[#31320] Re: [rubysoc] Queue C-extension patch to come — Ricardo Panaggio <panaggio.ricardo@...> 2010/07/16

Sorry for leaving this thread for so long. I've tried to finish the

[#31322] Re: [rubysoc] Queue C-extension patch to come — Aaron Patterson <aaron@...> 2010/07/16

On Sat, Jul 17, 2010 at 06:55:35AM +0900, Ricardo Panaggio wrote:

[#31324] Re: [rubysoc] Queue C-extension patch to come — Caleb Clausen <vikkous@...> 2010/07/17

NB: I am Ricardo's mentor for this project.

[#31331] Re: [rubysoc] Queue C-extension patch to come — Benoit Daloze <eregontp@...> 2010/07/17

On 17 July 2010 06:00, Caleb Clausen <vikkous@gmail.com> wrote:

[#31332] Re: [rubysoc] Queue C-extension patch to come — Caleb Clausen <vikkous@...> 2010/07/17

On 7/17/10, Benoit Daloze <eregontp@gmail.com> wrote:

[#31138] Why is there no standard way of creating a String from a char *? — Nikolai Weibull <now@...>

Hi!

14 messages 2010/07/08
[#31146] Re: Why is there no standard way of creating a String from a char *? — Urabe Shyouhei <shyouhei@...> 2010/07/09

(2010/07/09 7:04), Nikolai Weibull wrote:

[#31149] Re: Why is there no standard way of creating a String from a char *? — Nikolai Weibull <now@...> 2010/07/09

On Fri, Jul 9, 2010 at 06:20, Urabe Shyouhei <shyouhei@ruby-lang.org> wrote:

[#31150] Re: Why is there no standard way of creating a String from a char *? — Urabe Shyouhei <shyouhei@...> 2010/07/09

(2010/07/09 18:28), Nikolai Weibull wrote:

[#31217] [Bug #3562] regression in respond_to? — Aaron Patterson <redmine@...>

Bug #3562: regression in respond_to?

14 messages 2010/07/12

[#31269] [Bug #3566] memory leak when spawning+joining Threads in a loop — Eric Wong <redmine@...>

Bug #3566: memory leak when spawning+joining Threads in a loop

14 messages 2010/07/13

[#31399] [Backport #3595] Theres no encoding to differentiate a stream of Binary data from an 8-Bit ASCII string — Dreamcat Four <redmine@...>

Backport #3595: Theres no encoding to differentiate a stream of Binary data from an 8-Bit ASCII string

17 messages 2010/07/21

[#31459] [Bug #3607] [trunk/r28731] Gem.path has disappeared? — Ollivier Robert <redmine@...>

Bug #3607: [trunk/r28731] Gem.path has disappeared?

22 messages 2010/07/23

[#31519] [Bug #3622] Net::HTTP does not wait to send request body with Expect: 100-continue — Eric Hodel <redmine@...>

Bug #3622: Net::HTTP does not wait to send request body with Expect: 100-continue

9 messages 2010/07/28

[ruby-core:31193] Re: [Bug #3140] gem activation has changed between 1.8 and 1.9

From: Yusuke ENDOH <mame@...>
Date: 2010-07-11 13:23:18 UTC
List: ruby-core #31193
Hi,

2010/7/8 Roger Pack <rogerdpack2@gmail.com>:
>> I've commited the patch to trunk.
>> I'll commit it to ruby_1_9_2 tomorrow unless any critical problem
>> is reported (such as build trouble on windows).
>
> Sorry to throw a wrench in this one...
> This used to work...
>
>
> C:\dev\ruby\downloads>ruby -v
> ruby 1.9.3dev (2010-07-08) [i386-mingw32]
>
> C:\dev\ruby\downloads>gem search rdoc
> C:/installs/ruby_trunk_installed/lib/ruby/gems/1.9.1/specifications/rdoc-data-2.5.1.gemspec:18:
> [BUG] gc_sweep(): unknown data type 0x0(0x230bd19)
> ruby 1.9.3dev (2010-07-08) [i386-mingw32]


An obvious critical problem was reported, so I didn't commit the
patch to ruby_1_9_2.

Because this patch consists of just Ruby-level fix, I guess that
another potential problem was stimulated or there was some sort
of mistake.
I heard from eban (not evan) that he re-tested this on mingw32
but didn't reproduce this problem.

Roger, could you re-try to build from scratch?  Could you apply
the test to ruby_1_9_2 and check it is reproducible?


I'm really disappointed that no one seems to investigate this
problem (except Luis's [ruby-core:31110]).  No one want this issue
to be fixed, right?  Otherwise, please think that it is a problem
as yourself.  At least, one who becomes a maintainer should show
readiness to work at times like this.
At this rate, 1.9.2 will be released with this issue left.

-- 
Yusuke Endoh <mame@tsg.ne.jp>

In This Thread