Join GitHub today
Anyone meet segment fault 11 on mac when run padrino command #2097
Do you want to request a feature or report a bug?
What is the current behavior?
Run any of padrino command , it will be segment fault 11.
I have raised a issue to ruby.
Which versions of Ruby, Padrino, Sinatra, Rack, OS are you using? Did this work in previous versions?
ruby 2.2, 2.3
1.using padrino 0.12.8 , same error .
3.using rbenv tried several ruby version , still same issue.
seems no workaround on mac....
but run other command like " thin start", it is quite well, only for padrino command.
Yes, Padrino can create a basic Padrino Project, after I reinstall 2.3.3 based on rbenv.
so It could be caused my specific project, Padrino works inside a new project.
maybe the problem is package a padrino project as a gem, I will try build again from scratch to see what happened.
it has same issue on above two build.
it seems related with package as a Gem, but this may not be the root cause.
I'm able to temporarily fix the segfaults by changing the last line of your
load Gem.bin_path("padrino-core", "padrino")
What I believe is happening is that Bundler looks at the
When Bundler generates a binstub with the line above, it normally puts the name of the Gem as it's first argument (
When you run your
You can solve this permanently by changing
gem.executables = ["new_talk"]
That said, your
#!/usr/bin/env ruby Dir.chdir(File.dirname(__FILE__)+'/..') # Start the app with Padrino::Server require 'bundler/setup' require 'padrino-core/cli/launcher' ARGV.unshift('start') if ARGV.first.nil? || ARGV.first.start_with?('-') Padrino::Cli::Launcher.start ARGV # Start the app with Rack::Server #require "rack" #Rack::Server.start