[#30589] [Bug #3391] Use single exclamation mark instead of double exclamation mark for IRB — Diego Viola <redmine@...>

Bug #3391: Use single exclamation mark instead of double exclamation mark for IRB

10 messages 2010/06/04

[#30672] [Bug #3411] Time.local 1916,5,1 #=> 1916-04-30 23:00:00 +0100 — Benoit Daloze <redmine@...>

Bug #3411: Time.local 1916,5,1 #=> 1916-04-30 23:00:00 +0100

12 messages 2010/06/08

[#30699] [Bug #3419] 1.9.2-preview3 possible bug with Rails 3 active_record sqlite_adapter — Joe Sak <redmine@...>

Bug #3419: 1.9.2-preview3 possible bug with Rails 3 active_record sqlite_adapter

9 messages 2010/06/09

[#30734] [Bug #3428] ri outputs ansi escape sequences even when stdout is not a tty — caleb clausen <redmine@...>

Bug #3428: ri outputs ansi escape sequences even when stdout is not a tty

11 messages 2010/06/11

[#30756] [Feature #3436] Spawn the timer thread lazily — Maximilian Gass <redmine@...>

Feature #3436: Spawn the timer thread lazily

15 messages 2010/06/13
[#32686] [Ruby 1.9-Feature#3436] Spawn the timer thread lazily — Mark Somerville <redmine@...> 2010/10/04

Issue #3436 has been updated by Mark Somerville.

[ruby-core:30795] Re: [Bug #3105] seg faults and bus errors with ruby 1.8.7 p249

From: Aaron Patterson <aaron@...>
Date: 2010-06-17 16:15:02 UTC
List: ruby-core #30795
On Thu, Jun 17, 2010 at 06:28:22AM +0900, Scott Windsor wrote:
> Issue #3105 has been updated by Scott Windsor.
> 
> 
> I've also been getting a large number of seg faults after upgrading to 1.8.7 patchlevel 249.  This is the new default for Ubuntu 10.04 and after I upgraded I've gotten repeated issues.
> 
> /usr/lib/ruby/gems/1.8/gems/activesupport-2.3.5/lib/active_support/dependencies.rb:313: [BUG] Segmentation fault
> ruby 1.8.7 (2010-01-10 patchlevel 249) [x86_64-linux]
> 
> I've also tried clearing out and re-install all of my gems, but that didn't help at all.  It seems to be crashing regularly in different areas of active support.  (Perhaps related to Marshall?).  What further information can I provide to help this out?

Hi Scott!

Have you tried reducing the gems you use and isolating the problem?

Can you possibly provide code to reproduce the problem? 

Are you able to reproduce the problem during your tests?

If you can reproduce the problem while testing, can you try running them
from gdb and providing a stack trace?

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

In This Thread