-
-
Notifications
You must be signed in to change notification settings - Fork 477
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 #13
Comments
|
🤦 Sorry for the noob bug report.
|
Ok, cool. See if the problem goes away by upgrading node to 0.4.5 (it might). I'm going to port glob to be just in js soon. It won't be quite as fast, but it will be way more stable and portable that way. |
Still have the problem on node 0.4.5. It's interesting; it really doesn't want that pattern - Porting to JavaScript: +1 :) |
You could maybe do If you could run it in gdb, I'd love a stack trace. Otherwise closing this for now. |
If you want to tell a gdb noob how, and I'd love to help :) Interestingly, the |
The "help" command is helpful :) |
Heh, seems this bug report is here to make me look bad... Sorry. Reading symbols from /home/christian/local/bin/node...done. Program received signal SIGSEGV, Segmentation fault. |
Ah, right, so, at that point, do this:
I can repro this on my linux box (was missing something obvious before). Here's what I'm seeing:
|
Yeah, solution is just to write this in JS. |
Cool. Thanks for being so helpful! |
Will be solved by #23 |
require("glob").glob("*/.js", function (err, paths) {})
The text was updated successfully, but these errors were encountered: