Issue #7672 has been reported by kgerrard (Ken Gerrard). ---------------------------------------- Bug #7672: Segmentation faults with ibm_db gem on three versions of 1.9.3 on MacOS X and Ubuntu https://bugs.ruby-lang.org/issues/7672 Author: kgerrard (Ken Gerrard) Status: Open Priority: Normal Assignee: Category: Target version: ruby -v: 1.9.3 =begin I have a DB2-backed Rails 3.1 project I’m looking to update to 3.2, which means I have to use a newer version of the ibm_db gem. I have no problem running a server with the newer gem, but the intensive Cucumber tests inevitably result in a segmentation fault. I can detect no pattern to where the crashes occur. I’m posting here ((<as recommended by Praveen Devarao at the ibm_db help forum|URL:http://rubyforge.org/forum/forum.php?thread_id=512...)). I’m hesitant because I read the ((<HowToReport|URL:http://bugs.ruby-lang.org/projects/ruby/wiki/HowToReport>)) page and I don’t have reproducing code as required, since the segmentation faults happen in different places. Sometimes instead of a segmentation fault, the process just hangs indefinitely. I’ve gathered and attached logs from all combinations of the following: * OSes: MacOS X 10.8.2, Ubuntu 12.10 * Ruby 1.9.3: p194, p286, p327 * ibm_db gem: 2.5.9, 2.5.11 Looks like I can’t attach more than ten files at once, I’ll attach the MacOS logs separately. I also have Ubuntu core dumps if that helps, too big to attach. Here is a sampling of crashes under 1.9.3-p194 on MacOS X: /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/activemodel-3.2.8/lib/active_model/attribute_methods.rb:431: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:414: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/activesupport-3.2.8/lib/active_support/core_ext/class/attribute.rb:98: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/cucumber-1.1.2/lib/cucumber/ast/step_invocation.rb:59cfp consistency error - send /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/ibm_db-2.5.10/lib/active_record/connection_adapters/ibm_db_adapter.rb:1929: METHOD[BUG] /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/ibm_db-2.5.10/lib/active_record/connection_adapters/ibm_db_adapter.rb:1929: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/json-1.7.5/lib/json/common.rb:155: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/sprockets-2.1.3/lib/sprockets/caching.rb:46: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/thin-1.3.1/lib/thin/headers.rb:27: [BUG] Segmentation fault /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/securerandom.rb:140: [BUG] Segmentation fault /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/time.rb:499: [BUG] object allocation during garbage collection phase /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/httprequest.rb:174: [BUG] cfp consistency error - call0 /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/httprequest.rb:399: [BUG] probable buffer overflow: 32 for 23 /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/httpversion.rb:30: [BUG] object allocation during garbage collection phase /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/log.rb:71: [BUG] Segmentation fault /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/utils.rb:214: [BUG] Segmentation fault In case the above is inadequate, the outputs of (({ruby -v})) for each version on each OS: MacOS X: * (({ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-darwin12.2.1]})) * (({ruby 1.9.3p286 (2012-10-12 revision 37165) [x86_64-darwin12.2.1]})) * (({ruby 1.9.3p327 (2012-11-10 revision 37606) [x86_64-darwin12.2.1]})) Ubuntu: * (({ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]})) * (({ruby 1.9.3p286 (2012-10-12 revision 37165) [x86_64-linux]})) * (({ruby 1.9.3p327 (2012-11-10 revision 37606) [x86_64-linux]})) Let me know if you need anything else! I’m definitely available to provide further logs and whatever is necessary to work through this. =end
[ruby-trunk - Bug #7672][Open] Segmentation faults with ibm_db gem on three versions of 1.9.3 on Mac
on 2013-01-07 23:12
[ruby-trunk - Bug #7672] Segmentation faults with ibm_db gem on three versions of 1.9.3 on MacOS X a
on 2013-01-07 23:16
Issue #7672 has been updated by kgerrard (Ken Gerrard). File macos-ibm_db-2.5.9-ruby-1.9.3-p327.crash added File macos-ibm_db-2.5.9-ruby-1.9.3-p194-console.txt added File macos-ibm_db-2.5.9-ruby-1.9.3-p194.crash added File macos-ibm_db-2.5.9-ruby-1.9.3-p286-console.txt added File macos-ibm_db-2.5.9-ruby-1.9.3-p286.crash added File macos-ibm_db-2.5.9-ruby-1.9.3-p327-console.txt added Here are the MacOS logs for ibm_db 2.5.9. ---------------------------------------- Bug #7672: Segmentation faults with ibm_db gem on three versions of 1.9.3 on MacOS X and Ubuntu https://bugs.ruby-lang.org/issues/7672#change-35271 Author: kgerrard (Ken Gerrard) Status: Open Priority: Normal Assignee: Category: Target version: ruby -v: 1.9.3 =begin I have a DB2-backed Rails 3.1 project I’m looking to update to 3.2, which means I have to use a newer version of the ibm_db gem. I have no problem running a server with the newer gem, but the intensive Cucumber tests inevitably result in a segmentation fault. I can detect no pattern to where the crashes occur. I’m posting here ((<as recommended by Praveen Devarao at the ibm_db help forum|URL:http://rubyforge.org/forum/forum.php?thread_id=512...)). I’m hesitant because I read the ((<HowToReport|URL:http://bugs.ruby-lang.org/projects/ruby/wiki/HowToReport>)) page and I don’t have reproducing code as required, since the segmentation faults happen in different places. Sometimes instead of a segmentation fault, the process just hangs indefinitely. I’ve gathered and attached logs from all combinations of the following: * OSes: MacOS X 10.8.2, Ubuntu 12.10 * Ruby 1.9.3: p194, p286, p327 * ibm_db gem: 2.5.9, 2.5.11 Looks like I can’t attach more than ten files at once, I’ll attach the MacOS logs separately. I also have Ubuntu core dumps if that helps, too big to attach. Here is a sampling of crashes under 1.9.3-p194 on MacOS X: /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/activemodel-3.2.8/lib/active_model/attribute_methods.rb:431: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:414: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/activesupport-3.2.8/lib/active_support/core_ext/class/attribute.rb:98: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/cucumber-1.1.2/lib/cucumber/ast/step_invocation.rb:59cfp consistency error - send /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/ibm_db-2.5.10/lib/active_record/connection_adapters/ibm_db_adapter.rb:1929: METHOD[BUG] /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/ibm_db-2.5.10/lib/active_record/connection_adapters/ibm_db_adapter.rb:1929: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/json-1.7.5/lib/json/common.rb:155: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/sprockets-2.1.3/lib/sprockets/caching.rb:46: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/thin-1.3.1/lib/thin/headers.rb:27: [BUG] Segmentation fault /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/securerandom.rb:140: [BUG] Segmentation fault /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/time.rb:499: [BUG] object allocation during garbage collection phase /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/httprequest.rb:174: [BUG] cfp consistency error - call0 /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/httprequest.rb:399: [BUG] probable buffer overflow: 32 for 23 /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/httpversion.rb:30: [BUG] object allocation during garbage collection phase /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/log.rb:71: [BUG] Segmentation fault /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/utils.rb:214: [BUG] Segmentation fault In case the above is inadequate, the outputs of (({ruby -v})) for each version on each OS: MacOS X: * (({ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-darwin12.2.1]})) * (({ruby 1.9.3p286 (2012-10-12 revision 37165) [x86_64-darwin12.2.1]})) * (({ruby 1.9.3p327 (2012-11-10 revision 37606) [x86_64-darwin12.2.1]})) Ubuntu: * (({ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]})) * (({ruby 1.9.3p286 (2012-10-12 revision 37165) [x86_64-linux]})) * (({ruby 1.9.3p327 (2012-11-10 revision 37606) [x86_64-linux]})) Let me know if you need anything else! I’m definitely available to provide further logs and whatever is necessary to work through this. =end
[ruby-trunk - Bug #7672] Segmentation faults with ibm_db gem on three versions of 1.9.3 on MacOS X a
on 2013-01-07 23:18
Issue #7672 has been updated by kgerrard (Ken Gerrard). File macos-ibm_db-2.5.11-ruby-1.9.3-p327.crash added File macos-ibm_db-2.5.11-ruby-1.9.3-p194-console.txt added File macos-ibm_db-2.5.11-ruby-1.9.3-p194.crash added File macos-ibm_db-2.5.11-ruby-1.9.3-p286-console.txt added File macos-ibm_db-2.5.11-ruby-1.9.3-p286.crash added File macos-ibm_db-2.5.11-ruby-1.9.3-p327-console.txt added And the MacOS logs for ibm_db 2.5.11. ---------------------------------------- Bug #7672: Segmentation faults with ibm_db gem on three versions of 1.9.3 on MacOS X and Ubuntu https://bugs.ruby-lang.org/issues/7672#change-35272 Author: kgerrard (Ken Gerrard) Status: Open Priority: Normal Assignee: Category: Target version: ruby -v: 1.9.3 =begin I have a DB2-backed Rails 3.1 project I’m looking to update to 3.2, which means I have to use a newer version of the ibm_db gem. I have no problem running a server with the newer gem, but the intensive Cucumber tests inevitably result in a segmentation fault. I can detect no pattern to where the crashes occur. I’m posting here ((<as recommended by Praveen Devarao at the ibm_db help forum|URL:http://rubyforge.org/forum/forum.php?thread_id=512...)). I’m hesitant because I read the ((<HowToReport|URL:http://bugs.ruby-lang.org/projects/ruby/wiki/HowToReport>)) page and I don’t have reproducing code as required, since the segmentation faults happen in different places. Sometimes instead of a segmentation fault, the process just hangs indefinitely. I’ve gathered and attached logs from all combinations of the following: * OSes: MacOS X 10.8.2, Ubuntu 12.10 * Ruby 1.9.3: p194, p286, p327 * ibm_db gem: 2.5.9, 2.5.11 Looks like I can’t attach more than ten files at once, I’ll attach the MacOS logs separately. I also have Ubuntu core dumps if that helps, too big to attach. Here is a sampling of crashes under 1.9.3-p194 on MacOS X: /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/activemodel-3.2.8/lib/active_model/attribute_methods.rb:431: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:414: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/activesupport-3.2.8/lib/active_support/core_ext/class/attribute.rb:98: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/cucumber-1.1.2/lib/cucumber/ast/step_invocation.rb:59cfp consistency error - send /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/ibm_db-2.5.10/lib/active_record/connection_adapters/ibm_db_adapter.rb:1929: METHOD[BUG] /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/ibm_db-2.5.10/lib/active_record/connection_adapters/ibm_db_adapter.rb:1929: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/json-1.7.5/lib/json/common.rb:155: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/sprockets-2.1.3/lib/sprockets/caching.rb:46: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/thin-1.3.1/lib/thin/headers.rb:27: [BUG] Segmentation fault /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/securerandom.rb:140: [BUG] Segmentation fault /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/time.rb:499: [BUG] object allocation during garbage collection phase /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/httprequest.rb:174: [BUG] cfp consistency error - call0 /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/httprequest.rb:399: [BUG] probable buffer overflow: 32 for 23 /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/httpversion.rb:30: [BUG] object allocation during garbage collection phase /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/log.rb:71: [BUG] Segmentation fault /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/utils.rb:214: [BUG] Segmentation fault In case the above is inadequate, the outputs of (({ruby -v})) for each version on each OS: MacOS X: * (({ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-darwin12.2.1]})) * (({ruby 1.9.3p286 (2012-10-12 revision 37165) [x86_64-darwin12.2.1]})) * (({ruby 1.9.3p327 (2012-11-10 revision 37606) [x86_64-darwin12.2.1]})) Ubuntu: * (({ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]})) * (({ruby 1.9.3p286 (2012-10-12 revision 37165) [x86_64-linux]})) * (({ruby 1.9.3p327 (2012-11-10 revision 37606) [x86_64-linux]})) Let me know if you need anything else! I’m definitely available to provide further logs and whatever is necessary to work through this. =end
[ruby-trunk - Bug #7672] Segmentation faults with ibm_db gem on three versions of 1.9.3 on MacOS X a
on 2013-01-08 00:06
Issue #7672 has been updated by kosaki (Motohiro KOSAKI). If the problem only occur when using ibm_db gem, only IBM have a chance to help you. Please don't think we have ESP, please don't expect we can consult IBM product. Sorry, I don't think we can help you. ---------------------------------------- Bug #7672: Segmentation faults with ibm_db gem on three versions of 1.9.3 on MacOS X and Ubuntu https://bugs.ruby-lang.org/issues/7672#change-35273 Author: kgerrard (Ken Gerrard) Status: Open Priority: Normal Assignee: Category: Target version: ruby -v: 1.9.3 =begin I have a DB2-backed Rails 3.1 project I’m looking to update to 3.2, which means I have to use a newer version of the ibm_db gem. I have no problem running a server with the newer gem, but the intensive Cucumber tests inevitably result in a segmentation fault. I can detect no pattern to where the crashes occur. I’m posting here ((<as recommended by Praveen Devarao at the ibm_db help forum|URL:http://rubyforge.org/forum/forum.php?thread_id=512...)). I’m hesitant because I read the ((<HowToReport|URL:http://bugs.ruby-lang.org/projects/ruby/wiki/HowToReport>)) page and I don’t have reproducing code as required, since the segmentation faults happen in different places. Sometimes instead of a segmentation fault, the process just hangs indefinitely. I’ve gathered and attached logs from all combinations of the following: * OSes: MacOS X 10.8.2, Ubuntu 12.10 * Ruby 1.9.3: p194, p286, p327 * ibm_db gem: 2.5.9, 2.5.11 Looks like I can’t attach more than ten files at once, I’ll attach the MacOS logs separately. I also have Ubuntu core dumps if that helps, too big to attach. Here is a sampling of crashes under 1.9.3-p194 on MacOS X: /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/activemodel-3.2.8/lib/active_model/attribute_methods.rb:431: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:414: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/activesupport-3.2.8/lib/active_support/core_ext/class/attribute.rb:98: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/cucumber-1.1.2/lib/cucumber/ast/step_invocation.rb:59cfp consistency error - send /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/ibm_db-2.5.10/lib/active_record/connection_adapters/ibm_db_adapter.rb:1929: METHOD[BUG] /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/ibm_db-2.5.10/lib/active_record/connection_adapters/ibm_db_adapter.rb:1929: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/json-1.7.5/lib/json/common.rb:155: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/sprockets-2.1.3/lib/sprockets/caching.rb:46: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/thin-1.3.1/lib/thin/headers.rb:27: [BUG] Segmentation fault /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/securerandom.rb:140: [BUG] Segmentation fault /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/time.rb:499: [BUG] object allocation during garbage collection phase /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/httprequest.rb:174: [BUG] cfp consistency error - call0 /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/httprequest.rb:399: [BUG] probable buffer overflow: 32 for 23 /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/httpversion.rb:30: [BUG] object allocation during garbage collection phase /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/log.rb:71: [BUG] Segmentation fault /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/utils.rb:214: [BUG] Segmentation fault In case the above is inadequate, the outputs of (({ruby -v})) for each version on each OS: MacOS X: * (({ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-darwin12.2.1]})) * (({ruby 1.9.3p286 (2012-10-12 revision 37165) [x86_64-darwin12.2.1]})) * (({ruby 1.9.3p327 (2012-11-10 revision 37606) [x86_64-darwin12.2.1]})) Ubuntu: * (({ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]})) * (({ruby 1.9.3p286 (2012-10-12 revision 37165) [x86_64-linux]})) * (({ruby 1.9.3p327 (2012-11-10 revision 37606) [x86_64-linux]})) Let me know if you need anything else! I’m definitely available to provide further logs and whatever is necessary to work through this. =end
on 2013-01-08 01:56
Issue #7672 has been updated by usa (Usaku NAKAMURA). Status changed from Open to Third Party's Issue ---------------------------------------- Bug #7672: Segmentation faults with ibm_db gem on three versions of 1.9.3 on MacOS X and Ubuntu https://bugs.ruby-lang.org/issues/7672#change-35274 Author: kgerrard (Ken Gerrard) Status: Third Party's Issue Priority: Normal Assignee: Category: Target version: ruby -v: 1.9.3 =begin I have a DB2-backed Rails 3.1 project I’m looking to update to 3.2, which means I have to use a newer version of the ibm_db gem. I have no problem running a server with the newer gem, but the intensive Cucumber tests inevitably result in a segmentation fault. I can detect no pattern to where the crashes occur. I’m posting here ((<as recommended by Praveen Devarao at the ibm_db help forum|URL:http://rubyforge.org/forum/forum.php?thread_id=512...)). I’m hesitant because I read the ((<HowToReport|URL:http://bugs.ruby-lang.org/projects/ruby/wiki/HowToReport>)) page and I don’t have reproducing code as required, since the segmentation faults happen in different places. Sometimes instead of a segmentation fault, the process just hangs indefinitely. I’ve gathered and attached logs from all combinations of the following: * OSes: MacOS X 10.8.2, Ubuntu 12.10 * Ruby 1.9.3: p194, p286, p327 * ibm_db gem: 2.5.9, 2.5.11 Looks like I can’t attach more than ten files at once, I’ll attach the MacOS logs separately. I also have Ubuntu core dumps if that helps, too big to attach. Here is a sampling of crashes under 1.9.3-p194 on MacOS X: /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/activemodel-3.2.8/lib/active_model/attribute_methods.rb:431: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:414: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/activesupport-3.2.8/lib/active_support/core_ext/class/attribute.rb:98: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/cucumber-1.1.2/lib/cucumber/ast/step_invocation.rb:59cfp consistency error - send /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/ibm_db-2.5.10/lib/active_record/connection_adapters/ibm_db_adapter.rb:1929: METHOD[BUG] /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/ibm_db-2.5.10/lib/active_record/connection_adapters/ibm_db_adapter.rb:1929: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/json-1.7.5/lib/json/common.rb:155: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/sprockets-2.1.3/lib/sprockets/caching.rb:46: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/thin-1.3.1/lib/thin/headers.rb:27: [BUG] Segmentation fault /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/securerandom.rb:140: [BUG] Segmentation fault /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/time.rb:499: [BUG] object allocation during garbage collection phase /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/httprequest.rb:174: [BUG] cfp consistency error - call0 /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/httprequest.rb:399: [BUG] probable buffer overflow: 32 for 23 /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/httpversion.rb:30: [BUG] object allocation during garbage collection phase /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/log.rb:71: [BUG] Segmentation fault /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/utils.rb:214: [BUG] Segmentation fault In case the above is inadequate, the outputs of (({ruby -v})) for each version on each OS: MacOS X: * (({ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-darwin12.2.1]})) * (({ruby 1.9.3p286 (2012-10-12 revision 37165) [x86_64-darwin12.2.1]})) * (({ruby 1.9.3p327 (2012-11-10 revision 37606) [x86_64-darwin12.2.1]})) Ubuntu: * (({ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]})) * (({ruby 1.9.3p286 (2012-10-12 revision 37165) [x86_64-linux]})) * (({ruby 1.9.3p327 (2012-11-10 revision 37606) [x86_64-linux]})) Let me know if you need anything else! I’m definitely available to provide further logs and whatever is necessary to work through this. =end
[ruby-trunk - Bug #7672] Segmentation faults with ibm_db gem on three versions of 1.9.3 on MacOS X a
on 2013-01-08 03:32
Issue #7672 has been updated by kgerrard (Ken Gerrard). Yeah, I understand, that’s what I thought would happen but I posted here at the IBM person’s insistence. Oh well! Thanks. ---------------------------------------- Bug #7672: Segmentation faults with ibm_db gem on three versions of 1.9.3 on MacOS X and Ubuntu https://bugs.ruby-lang.org/issues/7672#change-35275 Author: kgerrard (Ken Gerrard) Status: Third Party's Issue Priority: Normal Assignee: Category: Target version: ruby -v: 1.9.3 =begin I have a DB2-backed Rails 3.1 project I’m looking to update to 3.2, which means I have to use a newer version of the ibm_db gem. I have no problem running a server with the newer gem, but the intensive Cucumber tests inevitably result in a segmentation fault. I can detect no pattern to where the crashes occur. I’m posting here ((<as recommended by Praveen Devarao at the ibm_db help forum|URL:http://rubyforge.org/forum/forum.php?thread_id=512...)). I’m hesitant because I read the ((<HowToReport|URL:http://bugs.ruby-lang.org/projects/ruby/wiki/HowToReport>)) page and I don’t have reproducing code as required, since the segmentation faults happen in different places. Sometimes instead of a segmentation fault, the process just hangs indefinitely. I’ve gathered and attached logs from all combinations of the following: * OSes: MacOS X 10.8.2, Ubuntu 12.10 * Ruby 1.9.3: p194, p286, p327 * ibm_db gem: 2.5.9, 2.5.11 Looks like I can’t attach more than ten files at once, I’ll attach the MacOS logs separately. I also have Ubuntu core dumps if that helps, too big to attach. Here is a sampling of crashes under 1.9.3-p194 on MacOS X: /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/activemodel-3.2.8/lib/active_model/attribute_methods.rb:431: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/activesupport-3.2.8/lib/active_support/callbacks.rb:414: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/activesupport-3.2.8/lib/active_support/core_ext/class/attribute.rb:98: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/cucumber-1.1.2/lib/cucumber/ast/step_invocation.rb:59cfp consistency error - send /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/ibm_db-2.5.10/lib/active_record/connection_adapters/ibm_db_adapter.rb:1929: METHOD[BUG] /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/ibm_db-2.5.10/lib/active_record/connection_adapters/ibm_db_adapter.rb:1929: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/json-1.7.5/lib/json/common.rb:155: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/sprockets-2.1.3/lib/sprockets/caching.rb:46: [BUG] Segmentation fault /Users/username/.rvm/gems/ruby-1.9.3-p194/gems/thin-1.3.1/lib/thin/headers.rb:27: [BUG] Segmentation fault /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/securerandom.rb:140: [BUG] Segmentation fault /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/time.rb:499: [BUG] object allocation during garbage collection phase /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/httprequest.rb:174: [BUG] cfp consistency error - call0 /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/httprequest.rb:399: [BUG] probable buffer overflow: 32 for 23 /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/httpversion.rb:30: [BUG] object allocation during garbage collection phase /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/log.rb:71: [BUG] Segmentation fault /Users/username/.rvm/rubies/ruby-1.9.3-p194/lib/ruby/1.9.1/webrick/utils.rb:214: [BUG] Segmentation fault In case the above is inadequate, the outputs of (({ruby -v})) for each version on each OS: MacOS X: * (({ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-darwin12.2.1]})) * (({ruby 1.9.3p286 (2012-10-12 revision 37165) [x86_64-darwin12.2.1]})) * (({ruby 1.9.3p327 (2012-11-10 revision 37606) [x86_64-darwin12.2.1]})) Ubuntu: * (({ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]})) * (({ruby 1.9.3p286 (2012-10-12 revision 37165) [x86_64-linux]})) * (({ruby 1.9.3p327 (2012-11-10 revision 37606) [x86_64-linux]})) Let me know if you need anything else! I’m definitely available to provide further logs and whatever is necessary to work through this. =end
Please log in before posting. Registration is free and takes only a minute.
Existing account
(Switch to SSL-encrypted connection)
NEW: Do you have a Google/GoogleMail or Yahoo account? No registration required!
Log in with Google account | Log in with Yahoo account
Log in with Google account | Log in with Yahoo account
No account? Register here.