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

Exits with Bus error: 10 #26

Closed
dgtlife opened this issue Nov 1, 2013 · 4 comments
Closed

Exits with Bus error: 10 #26

dgtlife opened this issue Nov 1, 2013 · 4 comments

Comments

@dgtlife
Copy link

dgtlife commented Nov 1, 2013

I have not yet been able to get this demo project to run yet. When I run:
$ ./rtd --debug

Selenium, Karma, and Meteor all start up fine ... then I see this:

Running "watch" task
[D] Task source: /Users/Derek/DGTLife/WebLab/meteor/meteor-rtd-example-project/test/rtd/node_modules/grunt-contrib-watch/tasks/watch.js
Waiting..../rtd: line 11: 22364 Bus error: 10           grunt --debug

and the process exits; then I'm back at the prompt.

I searched for the "Bus error: 10" in this issue queue, but no one seems to have experienced this. I'm running on a MBP with OS X Mavericks with:

node v0.10.20
meteor 0.6.6.2 which I switch down to 0.6.5.1 for rtd
phantomjs 1.9.2-2
karma 0.10.4
grunt-cli v0.1.9
grunt v0.4.1
jasmine-node 1.11.0
istanbul 0.1.44

Any thoughts on which component is complaining about the bus error?

@xolvio
Copy link
Collaborator

xolvio commented Nov 1, 2013

First time I've seen BUS error! I just got a MBP running OSX M as well so I'll give it a spin and report back...

@xolvio
Copy link
Collaborator

xolvio commented Nov 1, 2013

Works here. Seems to be a problem with the way node is installed. Check here:

gruntjs/grunt-contrib-watch#204

Hope that helps

@xolvio xolvio closed this as completed Nov 1, 2013
@xolvio xolvio reopened this Nov 1, 2013
@xolvio
Copy link
Collaborator

xolvio commented Nov 1, 2013

Let me know how you go

@dgtlife
Copy link
Author

dgtlife commented Nov 1, 2013

Yup. I moved up to node 0.10.21 and all components are happy now. Thanks for the quick response.
PS: I stayed on 0.10.20 because Meteor 0.6.6.2 is still tracking that version. Hopefully, this node upgrade doesn't precipitate other issues :-)

@dgtlife dgtlife closed this as completed Nov 1, 2013
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