[#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:31119] Re: [Bug #3549] Segfault when using god

From: Aaron Patterson <aaron@...>
Date: 2010-07-08 03:25:27 UTC
List: ruby-core #31119
On Thu, Jul 08, 2010 at 10:47:54AM +0900, David Kelso wrote:
> Bug #3549: Segfault when using god
> http://redmine.ruby-lang.org/issues/show/3549
> 
> Author: David Kelso
> Status: Open, Priority: Normal
> ruby -v: 1.9.2 rc1
> 
> I'm in the middle of upgrading our servers to 1.9.2 rc 1.
> 
> I'm running into this segfault when trying to start god.
> http://pastie.org/1035298
> 
> The file in question is viewable here:
> http://github.com/mojombo/god/blob/master/lib/god/event_handler.rb
> 
> I compiled ruby from source using this file
> ftp://ftp.ruby-lang.org//pub/ruby/ruby-1.9.2-rc1.tar.gz
> 
> I'm on Ubuntu 9.10
> 
> I don't know a thing about ruby internals, but let me know what info is needed and I'll hopefully be able to provide it!

No problem!  Thanks for reporting a bug.  Could you possibly provide us
with a little bit more info:

1. Does this happen every time you start up god?

2. Can you provide us with a script that reproduces the error?  If not:

3. Can you provide us with a gdb backtrace?  The way to get a backtrace
is like this:

  $ gdb /path/to/ruby
  (gdb) run -S /path/to/script scriptargs

The above part should run your script.  Once you get a segmentation
fault, you'll be dropped back to the gdb shell.  Execute the "bt" command like
so:

  (gdb) bt

Send us that back trace.

Any other info you can provide, like the type of hardware and compile
options you used to build ruby would be helpful too!

Thanks!

-- 
Aaron Patterson
http://tenderlovemaking.com/

In This Thread