Skip to content

segmentation fault - at a loss as to cause? #188

@bigteejay

Description

@bigteejay

me@:path$ grunt -v
Initializing
Command-line options: --verbose

Reading "Gruntfile.js" Gruntfile...OK

Registering Gruntfile tasks.

{blah blah...}

Registering "grunt-karma" local Npm module tasks.
Reading /home/user/path/node_modules/grunt-karma/package.json...OK
Parsing /home/user/path/node_modules/grunt-karma/package.json...OK
Segmentation fault (core dumped)

Dell, laptop (working fine otherwise)...

Distributor ID: Ubuntu
Description: Ubuntu 15.10
Release: 15.10
Codename: wily

Nodejs...

v5.10.1

Grunt...

grunt-cli v1.2.0
grunt v0.4.5

Running top while running grunt task showed no excessive resource usage.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions