search

tenderlove / neversaydie

NeverSayDie will let you rescue from SEGV's and is evil
57 stars 8 forks source link

Not working in production mode #1

Open mayanks opened 13 years ago

mayanks commented 13 years ago

Thank you for this awesome plugin. We have a heavy C++ engine which we run as a shared library and front-end with Rails. I used Neversaydie plugin to catch SEGV faults on the local development server, but when I deploy it, I am not able to catch the same exceptions. My production environment in nginx+passenger. I suspect passenger is hijacking the SEGV fault handler and not letting the Neversaydie plugin take control.

Can you suggest any way to debug this issue?

drbrain commented 13 years ago

Um… how do I even respond to this?

If you're USING neversaydie to hide a problem you're doing it WRONG.

You need to fix the source of the segmentation faults, not hide them with neversaydie. If you use neversaydie to hide your segmentation faults you'll corrupt your data, kill unicorns and the mythical narwhal and make children cry.

You don't want the children to cry.

Please, PLEASE‼ Think of the children‼‼

mayanks commented 13 years ago

I am not trying to hide the problem. I just don't want my users to see 502 Bad Gateway error and at the same time notified myself about this crash with proper backtrace so I could fix the problem.

Whoever said I wanted to see children cry.