Sitelet https://github.com/nodejs/node/issues/2561
Skip to content

segfault with v3.1.0 and possibly --harmony-arrow-functions #2561

Description

@freak4pc

When trying to run the following
iojs --harmony-arrow-functions dreamdate.js

This issue isn't happening in io.js v2.5.0 , and also doesn't happen on io.js v3.0.
Starts from v3.1.0.

screen shot 2015-08-26 at 4 49 53 pm

Activity

  1. mscdex commented on Aug 26, 2015

    @mscdex
    Contributor

    Can you produce a minimal, reproducible example? What platform is this on?

    I just tried a simple script (with --harmony-arrow-functions) that used fat arrows on v3.1.0 on Linux and did not encounter this issue.

  2. freak4pc commented on Aug 26, 2015

    @freak4pc
    Author

    It seems to work fine here as well with a smaller sample,
    So I guess it's not directly related to --harmony-arrow-functions

    The following script works fine on 3.2.0 :

    'use strict'
    
    let callback = (name) => {
            console.log("hello " + name)
    }
    
    callback("shai")

    But specifically when running my server (which works fine on 2.5.0 as well as 3.0.0) , it crashes with a Segfault.

    Is there any way to get more verbose output so I can give a better direction for this?

    Thank you

  3. silverwind commented on Aug 26, 2015

    @silverwind
    Contributor

    What OS is that? Try running it through either gdb or lldb, for example lldb -- iojs file.js and then r and probably bt.

  4. added
    c++Issues and PRs that require attention from people who are familiar with C++.
    on Aug 26, 2015
  5. ChALkeR commented on Aug 26, 2015

    @ChALkeR
    Member

    See #1655 just in case.

  6. yoshuawuyts commented on Aug 31, 2015

    @yoshuawuyts

    Not sure if related, but found an issue where 0.12.x gives an ECONNREFUSED error, 3.2.0 segfaults. Can create a separate issue if not related.

    img
    screen shot 2015-08-31 at 12 40 41

    txt

    ~/src/dlivr/api master
    ❯ npm start
    
    > api@1.0.0 start /Users/yw/src/dlivr/api
    > node .
    
    zsh: segmentation fault  npm start
    
    ~/src/dlivr/api master
    ❯ node -v
    v3.2.0
    
    ~/src/dlivr/api master
    ❯ nvm use 0.12
    ^[kkNow using node v0.12.7 (npm v2.11.3)
    
    ~/src/dlivr/api master
    ❯ npm start
    
    > api@1.0.0 start /Users/yw/src/dlivr/api
    > node .
    
    {"name":"log","type":"static","message":"debug"}
    {"name":"port","message":1337,"type":"static"}
    {"name":"env","message":"development","type":"static"}
    Knex:Error Pool2 - Error: connect ECONNREFUSED
    Knex:Error Pool2 - Error: connect ECONNREFUSED
    ^C
    
    ~/src/dlivr/api master  2m 20s
    ❯ nvm use 3
    Now using io.js v3.2.0 (npm v2.13.3)
  7. Fishrock123 commented on Aug 31, 2015

    @Fishrock123
    Contributor

    @yoshuawuyts can you open a new issue?

    Also, can both of you use either lldb or gdb, or mdb to get a thorough breakdown of what is happening in the segfault? Feel free to ask if you need more info, setting this stuff up isn't particularly trivial.

  8. changed the title [-]Super odd Issue - 23267 segmentation fault[/-] [+]segfault with v3.1.0 and possibly --harmony-arrow-functions[/+] on Aug 31, 2015
  9. yoshuawuyts commented on Aug 31, 2015

    @yoshuawuyts

    @Fishrock123 I'm willing to run that, but could you point me in the right direction on how to set that up? Thanks!

  10. Fishrock123 commented on Aug 31, 2015

    @Fishrock123
    Contributor

    Been a while since I did it. @thlorenz has a guide here for lldb on OS X: https://gist.github.com/thlorenz/30bf0a3f67b1d97b2945 (Not sure if it is up-to-date, when I did it I didn't patch lldb and it worked?)

  11. Fishrock123 commented on Aug 31, 2015

    @Fishrock123
    Contributor

    @freak4pc Could you let us know what OS you're seeing this on at least? :)

  12. freak4pc commented on Sep 1, 2015

    @freak4pc
    Author

    Sorry guys, I'm pretty much flooded with work now.
    I'll try to get more info from lldb tomorrow and post it here...

  13. evanlucas commented on Oct 20, 2015

    @evanlucas
    Contributor

    is this still an issue in the latest stable (v4.2.1 as of now)?

  14. evanlucas commented on Nov 9, 2015

    @evanlucas
    Contributor

    Closing due to inactivity and the fact that arrow functions are no longer behind a flag as of v4. If this is still an issue please feel to reopen. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    c++Issues and PRs that require attention from people who are familiar with C++.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions