-
Notifications
You must be signed in to change notification settings - Fork 54
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@extend causing a coredump #165
Comments
This is likely fixed by 3.3.6 See sass/libsass#2017 sass/libsass#2031 which we cannot upgrade to due to sass/libsass#2046 (We tried to here: #149). We'll probably have to wait until they drop 3.4 (hopefully soon!): sass/libsass#2174 I can confirm your bug:
I can also confirm that upgrading (when we can!) will fix it:
Going to close this as it's an exact duplicate of an upstream bug and hopefully we'll be able to upgrade soon :) |
Ah, i presumed something like this when readed another closed issues here. I'll keep watching about next update. Thanks for your reply! |
3.3.6 is now available via 0.11.2 🎉 |
Hi,
I found an obscure bug that cause a coredump, here you can see a sample source on SassMeister:
https://gist.github.com/sveetch/99fa86f9716b020d1cb19e869b20971a
Using it from commandline :
sassc sample.scss
It results in:
Segmentation fault (core dumped)
And nothing else in the output.
Basically i was trying to compile this using my Boussole project, so through your
sass
module and finally tried directly with sassc commandline tool to isolate the bug.Finally i tried this sample code on SassMeister with any available compiler and always have a correct return output. Also i successfully compiled this code with Compass 1.0.1.
The text was updated successfully, but these errors were encountered: