From: "ko1 (Koichi Sasada)" Date: 2013-02-17T13:54:57+09:00 Subject: [ruby-core:52321] [ruby-trunk - Bug #7350] Segmentation fault with ruby 1.9.3p328 (2012-11-13) [x86_64-linux] Issue #7350 has been updated by ko1 (Koichi Sasada). Assignee set to mame (Yusuke Endoh) ---------------------------------------- Bug #7350: Segmentation fault with ruby 1.9.3p328 (2012-11-13) [x86_64-linux] https://bugs.ruby-lang.org/issues/7350#change-36364 Author: ggiesemann (Geoffrey Giesemann) Status: Feedback Priority: Normal Assignee: mame (Yusuke Endoh) Category: Target version: 2.0.0 ruby -v: ruby 1.9.3p328 (2012-11-13) [x86_64-linux] I'm experiencing sporadic segmentation faults in a ruby daemon running with: ruby 1.9.3p328 (2012-11-13) [x86_64-linux] This is actually the 1.9.3p327 ruby patched with https://github.com/ruby/ruby/commit/ae2df330 as the issue http://bugs.ruby-lang.org/issues/7123 looked similar to the one I was experiencing. The daemon in question sits in a loop pulling messages out of an ActiveMQ server using the stomp gem; DOM parsing a file locally using libxml-ruby; then stuffing another message back on to the server using the same stomp client. I haven't been able to isolate the problem into a smaller block; but I can reproduce it in ~15 minutes on an AWS test server. I've included two examples of crash output, I have several more from 1.9.3p286. Happy to try patches or anything further to help debug/diagnose the issue. -- http://bugs.ruby-lang.org/