Bugs item #3683, was opened at 2006-02-28 10:33 You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1698&aid=3683&group_id=426 Category: Core Group: None Status: Open Resolution: None Priority: 3 Submitted By: Payton Swick (brillig) Assigned to: Nobody (None) Summary: rails segfaults at 2nd load with eval.c: No such file or directory. Initial Comment: When running a rails app using webrick or mongrel, I can load any given page (involving a controller) once, and any subsequent page loads trigger a "Segmentation fault". This problem is very new, and has only started occurring since I last updated my Gentoo linux system. The bug was submitted to Gentoo, but they believe it to be a ruby issue: http://bugs.gentoo.org/show_bug.cgi?id=123718 I did try recompiling ruby and reinstalling the rails gem (as well as activerecord, actionpack, actionmailer, actionwebservice, activesupport). I use ruby and rubygems from portage, but I use rails and associated packages from gems. I'm using ruby-1.8.4-r1 and rubygems-0.8.11. (I have also tried rubygems-0.8.11-r3, rubygems-0.8.11-r4, and ruby-1.8.4.20060226). I was loading ruby-mysql, but I have since disabled activerecord, and there has been no change in the problem. Here's my test case: $ rails testing $ cd testing $ ruby ./script/server # webrick starts $ wget http://localhost:3000/ # This works fine, no matter how many times it loads the HTML. $ wget http://localhost:3000/test # ERROR 404: Not Found. $ wget http://localhost:3000/test # ERROR 404: Not Found. $ wget http://localhost:3000/test # ERROR 500: Internal Server Error. $ wget http://localhost:3000/test # No data received. # At this point, webrick has segfaulted. The beginning of the segfault, with debug symbols enabled, looks like this: Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 16384 (LWP 2768)] rb_eval (self=7907598, n=0xb75ae860) at eval.c:2879 2879 eval.c: No such file or directory. in eval.c A full backtrace is available on the gentoo bug report. -Payton ---------------------------------------------------------------------- You can respond by visiting: http://rubyforge.org/tracker/?func=detail&atid=1698&aid=3683&group_id=426