Skip to content
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

Segfault on nodejs build #100

Open
IvanSanchez opened this issue May 27, 2015 · 0 comments
Open

Segfault on nodejs build #100

IvanSanchez opened this issue May 27, 2015 · 0 comments

Comments

@IvanSanchez
Copy link

Steps to reproduce:

  • Clone repo
  • Run npm install to trigger build (will call node-gyp rebuild internally)
  • Run build/Release/glslOptimizer.node
  • Segfault!

Fiddling around with gdb I'm able to get:

(gdb) run
Starting program: glsl-optimizer/build/Release/obj.target/glslOptimizer.node 

Program received signal SIGSEGV, Segmentation fault.
_mesa_glsl_parse_state::has_uniform_buffer_objects (this=0x0) at ../src/glsl/glsl_parser_extras.h:197
197           return ARB_uniform_buffer_object_enable || is_version(140, 300);
(gdb) quit

On a related note, #92 is reproducible on my machine (Debian 8, quadcore i5, linux kernel v4.0.0-1-amd64) . I somehow suspect a bad build via cmake might be related to a segfault-y build via gyp.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant