"Segmentation fault ruby 1.8.6" "i686-linux" "patchlevel 230"
Reported by Tobi Reif | June 30th, 2008 @ 11:36 AM | in 2.x
When I reported #512, I tried to reproduce the issue in order to provide the full stack trace. Instead I got this:
$ ./script/server -e test -p 2000
=> Booting Mongrel (use 'script/server webrick' to force WEBrick)
=> Rails 2.1.0 application starting on http://0.0.0.0:2000
=> Call with -d to detach
=> Ctrl-C to shutdown server
** Starting Mongrel listening at 0.0.0.0:2000
** Starting Rails with test environment...
** Rails loaded.
** Loading any Rails specific GemPlugins
** Signals ready. TERM => stop. USR2 => restart. INT => stop (no restart).
** Rails signals registered. HUP => reload (without restart). It might not work well.
** Mongrel 1.1.5 available at 0.0.0.0:2000
** Use CTRL-C to stop.
/usr/local/lib/ruby/gems/1.8/gems/actionpack-2.1.0/lib/action_view/helpers/form_tag_helper.rb:431: [BUG] Segmentation fault
ruby 1.8.6 (2008-06-20) [i686-linux]
Aborted
$ ruby -v
ruby 1.8.6 (2008-06-20 patchlevel 230) [i686-linux]
$
Comments and changes to this ticket
-
Tobi Reif October 23rd, 2008 @ 04:22 PM
It might be purely a Ruby bug, see http://rubyforge.org/tracker/?fu...
-
Tobi Reif July 2nd, 2008 @ 04:03 PM
It's a Ruby issue, and it seems to be resolved:
http://redmine.ruby-lang.org/iss...
(I'd delete this ticket if I could find a way to do that.)
-
Joshua Peek July 13th, 2008 @ 08:34 PM
- → State changed from “new” to “invalid”
- → Title changed from “"Segmentation fault ruby 1.8.6" "i686-linux" "patchlevel 230"” to “"Segmentation fault”
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
The Git repository resides at http://github.com/rails
Check out the current development trunk (Edge Rails) with:
git clone git://github.com/rails/rails.git
Creating or reviewing a patch
See the contributor guide.
Creating a feature request
Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".
