Capture segmentation fault backtraces from Ruby and Resque on Linux?

Check out Hoptoad getExceptional and New Relic All are SaaS options that will do this for you (New Relic will also track performance). If you want to roll your own, try the exception_notification gem.

Check out Hoptoad, getExceptional, and New Relic. All are SaaS options that will do this for you (New Relic will also track performance). If you want to roll your own, try the exception_notification gem.

We already have tools for catching Ruby-level exceptions. We need tools to catch segmentation faults and bus errors in the Ruby process itself. Do any of the tools you suggested do this?

Googling for "Hoptoad segmentation fault" does not turn up any instructions. – emk Oct 28 '10 at 12:41 No, unfortunately these require the Ruby interpreter to be still running. Sorry I missed the "segmentation fault" part.At this point, it's really not a Ruby question anymore.

Server fault may be your best bet. – Mark Thomas Oct 28 '10 at 19:38.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.