Issue #7350 has been updated by mame (Yusuke Endoh).

Status changed from Open to Feedback
Target version set to 2.0.0

Could you show the small code sample?
I'm very happy if you kindly show the process to setup STOMP server :-)
We can make no progress without it.

-- 
Yusuke Endoh <mame / tsg.ne.jp>
----------------------------------------
Bug #7350: Segmentation fault with ruby 1.9.3p328 (2012-11-13) [x86_64-linux]
https://bugs.ruby-lang.org/issues/7350#change-33804

Author: ggiesemann (Geoffrey Giesemann)
Status: Feedback
Priority: Normal
Assignee: 
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/