Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

segmentation fault when parsing invalid sass #7

Closed
mauritslamers opened this issue May 31, 2012 · 6 comments
Closed

segmentation fault when parsing invalid sass #7

mauritslamers opened this issue May 31, 2012 · 6 comments

Comments

@mauritslamers
Copy link
Contributor

This is both a sort of proposal as well as an issue:
If invalid css is being used, the module segfaults.

So proposal is to do a normal node-style callback with cb(err,result) and to catch the segfault in some way.

Example css used:

$theme: 'ace';
$theme.checkbox {
  border: 0px none;

  &.disabled {
    opacity: .5;
  }
}
@andrew
Copy link
Contributor

andrew commented May 31, 2012

Yes definitely, the C++ code in bindings.cpp needs to hand back the error to node, it's on my todo list for this weekend,

@johnraz
Copy link

johnraz commented Jun 6, 2014

Mmm this one is quite old and I can't find any way to get more output on my syntax error... Any workaround / advice ?
edit: linting is obviously one option ;)

@chrisspiegl
Copy link

+1

Looks like this problem is not fixed? I get the segmentation fault while using node-sass with gulp-sass.

@keithamus
Copy link
Member

@cspiegl you should raise a new issue if it is still present

@ConnorAtherton
Copy link

Same as @cspiegl above.

@keithamus
Copy link
Member

@ConnorAtherton please add comments to #378.

@sass sass locked and limited conversation to collaborators Jul 31, 2014
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants