When I run a cron, using whenever gem, the script is executed but I get
an error saying its a "[BUG] Segmentation fault" and I get a rather big
core file in my app each time. Can I ignore it? If yes I can just delete
any core files with another cron.
--
Posted via http://www.ruby-forum.com/.
hm not realy, a "Segmentation fault" is a break, mostly an dereference
of a null pointer, into the program which cause it to close. you can not
catch it and you should not ignore it ... when did it happen?
--
Posted via http://www.ruby-forum.com/.
Can you? Yes. Should you? Probably not.
Kind of like continuing to drive a car with the "CHECK ENGINE" light
on the dashboard lit up and flashing... "Wait, what's that smell?" 
On Sat, Jul 16, 2011 at 10:43 AM, Paul Bergstrom <pal@palbergstrom.com> wrote:
When I run a cron, using whenever gem, the script is executed but I get
an error saying its a "[BUG] Segmentation fault" and I get a rather big
core file in my app each time. Can I ignore it?
--
Hassan Schroeder ------------------------ hassan.schroeder@gmail.com
twitter: @hassan
If your on BSD you can set kern.sugid_coredump to turn off core dumps.
You should investigate the problem though.
On Sat, Jul 16, 2011 at 12:43 PM, Paul Bergstrom <pal@palbergstrom.com> wrote:
When I run a cron, using whenever gem, the script is executed but I get
an error saying its a "[BUG] Segmentation fault" and I get a rather big
core file in my app each time. Can I ignore it? If yes I can just delete
any core files with another cron.--
Posted via http://www.ruby-forum.com/\.
Stu wrote in post #1011265:
If your on BSD you can set kern.sugid_coredump to turn off core dumps.
On other platforms it might be
$ ulimit -c 0
You should investigate the problem though.
Certainly!
Cheers
--
Posted via http://www.ruby-forum.com/\.