Bug #9594
closedSegfault in 2.1.1 follows cont from debugger (Rails 4.0.3, debugger 1.6.6, rspec, os x mavericks 1.9.2)
Description
Thought I'd post this, let me know if I can help with more info.
I've experienced it in a number of different places. No segfaults occurring when debugger is not used.
matt@foo taxonworks (master *%)$ rspec spec/lib/material_spec.rb
[Coveralls] Set up the SimpleCov formatter.
[Coveralls] Using SimpleCov's default settings.
........./Users/matt/src/taxonworks/lib/material.rb:23
object.biocuration_classes << BiocurationClass.find(opts[:collection_objects][o][:biocuration_classes]) 
[18, 27] in /Users/matt/src/taxonworks/lib/material.rb
   18        object = stub_object.clone
   19        object.total = opts[:collection_objects][o][:total]
   20  
   21        if opts[:collection_objects][o][:biocuration_classes] 
   22         debugger 
=> 23          object.biocuration_classes << BiocurationClass.find(opts[:collection_objects][o][:biocuration_classes]) 
   24        end
   25  
   26        object.notes << note.clone if note
   27        object.container = container if container
(rdb:1) cont
/Users/matt/.rvm/gems/ruby-2.1.1/gems/activerecord-4.0.3/lib/active_record/attribute_methods.rb:149: [BUG] Segmentation fault at 0x00000000000018
ruby 2.1.1p76 (2014-02-24 revision 45161) [x86_64-darwin13.0]
Files
        
           Updated by mrkn (Kenta Murata) over 11 years ago
          Updated by mrkn (Kenta Murata) over 11 years ago
          
          
        
        
      
      - Status changed from Open to Feedback
Is this reproduced with byebug instead of debugger?
        
           Updated by nobu (Nobuyoshi Nakada) over 11 years ago
          Updated by nobu (Nobuyoshi Nakada) over 11 years ago
          
          
        
        
      
      - File bug-9594.log bug-9594.log added
- Description updated (diff)
        
           Updated by nobu (Nobuyoshi Nakada) over 11 years ago
          Updated by nobu (Nobuyoshi Nakada) over 11 years ago
          
          
        
        
      
      - File bug-9594.log bug-9594.log added
On MacOS X, a crash log file under ~/Library/Logs/DiagnosticReports is important.
        
           Updated by mjy (Matt Yoder) over 11 years ago
          Updated by mjy (Matt Yoder) over 11 years ago
          
          
        
        
      
      Kenta Murata wrote:
Is this reproduced with byebug instead of debugger?
No, using byebug (2.7.0) in the same way does not reproduce the bug (thanks for pointing this gem out btw).
        
           Updated by mjy (Matt Yoder) over 11 years ago
          Updated by mjy (Matt Yoder) over 11 years ago
          
          
        
        
      
      Nobuyoshi Nakada wrote:
On MacOS X, a crash log file under
~/Library/Logs/DiagnosticReportsis important.
Attached here.
        
           Updated by acrogenesis (Adrian Rangel) over 11 years ago
          Updated by acrogenesis (Adrian Rangel) over 11 years ago
          
          
        
        
      
      - File ruby_2014-03-13-140628_Adrians-MacBook-Pro-3.crash ruby_2014-03-13-140628_Adrians-MacBook-Pro-3.crash added
This is also happening to me when using debugger
Ruby 2.1.0, Mavericks 10.9.3 (Build 13D12), rails 4.0.3, debugger 1.6.6, rspec-rails 2.14.1
/Users/Adrian/.rvm/gems/ruby-2.1.0/gems/activerecord-4.0.3/lib/active_record/attribute_methods.rb:149: [BUG] Segmentation fault at 0x00000000000018
ruby 2.1.0p0 (2013-12-25 revision 44422) [x86_64-darwin12.0]
        
           Updated by abinoam (Abinoam P. Marques Jr.) over 11 years ago
          Updated by abinoam (Abinoam P. Marques Jr.) over 11 years ago
          
          
        
        
      
      On debugger gem repository:
- https://github.com/cldwalker/debugger/issues/114 - Same segfault
- https://github.com/cldwalker/debugger/issues/47 - Ruby 2.0.0 is not officially supported by debugger gem
- https://github.com/cldwalker/debugger/issues/69 - Somebody is trying to help the maintainer to port the code for 2.0.0 compatibility...
- https://github.com/cldwalker/debugger/issues/89#issuecomment-26330015 - Because the maintainer is facing some problems in having time to do it.
- https://github.com/deivid-rodriguez/byebug - Some people are using byebug instead.
        
           Updated by jeremyevans0 (Jeremy Evans) over 6 years ago
          Updated by jeremyevans0 (Jeremy Evans) over 6 years ago
          
          
        
        
      
      - Status changed from Feedback to Third Party's Issue
- Backport deleted (1.9.3: UNKNOWN, 2.0.0: UNKNOWN, 2.1: UNKNOWN)