I'm getting the following error when trying to save in Codekit
/Applications/CodeKit.app/Contents/Resources/engines/oilypng/lib/oily_png/oily_png.bundle [BUG] Segmentation fault
ruby 1.9.3p286 (2012-10-12 revision 37165) [x86_64-darwin12.2.0]
Anyone know what I need to fix?
Edit
I think it has something to do with Compass being unable to Compile. Compass is installed and everything was working up until today. I updated Codekit to version 1.6.1 today
Try doing compass clean inside your project folder and then compile again.
Related
Background: I am using Helix to write a native extension for Ruby, written in Rust. On my 64bit MacBook Pro, everything works fine, I am experiencing this problem on a 32bit Linux machine (i686-unknown-linux-gnu). The problem occurs regardless of the code in the Rust source.
The shared object compiles fine, but if I try to require it, I invariably get an error like the following:
`require': invalid symbol in encoding US-ASCII :"(}\xC3\xBFtO\xEE\xB7\xE0\xEBi\x01\xAC|\xC3\xBF\x18.\x8D\xB5\xC6\xC0\x89\xB5\xFD\xF1\x8B\xB5\x80\x8B\x91\x01\x18.\x8D\xB5\xB7\xC0\x89\xB5\xE0|\xC3\xBF\xFA\x8Ck" (EncodingError)
On different invocations of Ruby, when I require the file, the binary string in the error message is different, which further perplexes me.
Steps to reproduce (required: Helix, Rust, Ruby, Bundler):
Note: I am using
Helix 0.7.5
cargo 1.30.0 (a1a4ad372 2018-11-02)
rustc 1.30.1 (1433507eb 2018-11-07)
ruby 2.6.0p0 (2018-12-25 revision 66547) [i686-linux]
Bundler version 1.17.2
But the same problem exists with the recommended versions from the Helix README, albeit compiled for 32 bit rather than 64 bit
Helix 0.7.5
cargo 0.18.0 (fe7b0cdcf 2017-04-24)
rustc 1.17.0 (56124baa9 2017-04-24)
ruby 2.4.1p111 (2017-03-22 revision 58053) [i686-linux]
Bundler version 1.14.6
mkdir repro
cd repro/
bundle init
echo 'gem "helix-rails"' > Gemfile
bundle
helix bootstrap example
cd example
bundle exec rake build
bundle exec ruby lib/example.rb
I've also opened issue 163 on the tildeio/helix repo.
I'm trying to get my build flow working, however I cannot seem to get it working. When Sass goes to run after I save a .scss file, I get the following error:
/.rvm/rubies/ruby-1.9.3-p545/lib/ruby/site_ruby/1.9.1/rubygems/dependency.rb:298:in 'to_specs': Could not find 'sass' (>= 0.a) among 20 total gem(s) (Gem::LoadError)
I'm not entirely sure what else I would need to provide, but hopefully this helps;
The FileWatcher is pointing to /Users/Nick/.rvm/gems/ruby-2.4.2/bin/sass
$ sass -v
Ruby Sass 3.5.6
$ ruby -v
ruby 2.4.2p198 (2017-09-14 revision 59899) [x86_64-darwin17]
$ which sass
/Users/Nick/.rvm/gems/ruby-2.4.2/bin/sass
$ which ruby
/Users/Nick/.rvm/rubies/ruby-2.4.2/bin/ruby
It turns out the issue was related specifically to High Sierra 10.13 that is a known bug. I updated to 10.13.6 and updated XCode Tools and everything is working as it should.
I've got a project using the following specification at Gemfile:
ruby '2.3.1', :engine => 'jruby', :engine_version => 'jruby-9.1.7.0'
and this was working fine under my old Debian 8.1 installation. But I decided to test Arch Linux and now I'm getting an error when I run
$ rvm install 2.3.1
The Error:
Segmentation fault (core file generated)
I've never faced an error like this and got no ideas about how to solve it. Any suggestions?
EDIT => As required, I posted all make.log file as a Github Gist. This is the link to it.
I am having a problem on my macbook pro when I run certain terminal commands. It seems to be tied to Ruby. I am on Yosemite 10.10.3.
I am using RVM for my ruby/rails stuff. Today I tried to run a 'sass watch' while working on some Foundation learning stuff. When I run the command and I get the following:
dhcp-uris-3626:foundation johndcowan$ sass --watch
ruby(3631,0x7fff7d721300) malloc: *** error for object 0x7faac2801808: incorrect checksum for freed object - object was probably modified after being freed.
*** set a breakpoint in malloc_error_break to debug
Abort trap: 6
When running the same sass --watch command on a subsequent time, I got a bit more info:
dhcp-uris-3626:foundation johndcowan$ sass --watch
[BUG] Segmentation fault
ruby 1.9.2p318 (2012-02-14 revision 34678) [x86_64-darwin11.3.0]
-- control frame ----------
c:0001 p:---- s:0002 b:0002 l:000001 d:000001 TOP
---------------------------
-- C level backtrace information -------------------------------------------
[NOTE]
You may have encountered a bug in the Ruby interpreter or extension libraries.
Bug reports are welcome.
For details: http://www.ruby-lang.org/bugreport.html
Abort trap: 6
I was using ruby-2.0.0-p247. I tried switching to ruby-1.9.2-p318 and running >> gem install sass. That also bombs when running sass --watch. When I switched to using ruby-1.9.3-p125 and ran gem install sass, everything works fine. Go figure.
I tried updating RVM, to no help.
I do not know how to fix the problem I am seeing and am hoping someone here can assist me.
You should re-install gem because it have native extension which usually related to correspond ruby version used during compilation of it. In some configurations (i.e. when you use vendor/bundle directory for store application gems) when you switching between ruby versions you can still use the gem installed with other ruby version.
We just created an compass project like described in the compass-inuit manual.
When we now start "compass watch" we get the following error message:
user#VirtualXubuntu:/tmp/compass-test/my_project$ compass watch
>>> Change detected at 12:23:22 to: sass/style.scss
error sass/sass/style.scss (Line 99: Invalid CSS after "}": expected "{", was "")
identical stylesheets/sass/style.css
>>> Compass is polling for changes. Press Ctrl-C to Stop.
Actually I don't know what this error means - since I'm a newbie in compass...
Version Info:
Ubuntu 12.10 [amd64]
ruby 1.9.3p194 (2012-04-20 revision 35410) [x86_64-linux]
Compass 0.12.2 (Alnilam)
This has been fixed in a newer version of the extension. Update by running gem install compass-inuit -v 4.5.5.1, then make a new project by running:
compass create my_project -r compass-inuit --using compass-inuit
I believe the cause of this error is one of the brackets isn't really a bracket but a pasted character. This causes the compiler to miss it and believe that a selector isn't closed.
Sorry for the hassle.