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

children(inPath:recursive:) crashes #122

Closed
dduan opened this issue Apr 2, 2020 · 0 comments · Fixed by #123
Closed

children(inPath:recursive:) crashes #122

dduan opened this issue Apr 2, 2020 · 0 comments · Fixed by #123

Comments

@dduan
Copy link
Owner

dduan commented Apr 2, 2020

in macOS 10.15.4 (19E266) + Swift 5.2

Screen Shot 2020-04-01 at 8 37 56 PM

dduan added a commit that referenced this issue Apr 3, 2020
On macOS 10.15.4, accessing data structure returned by `scandir`
occassionally returns a mysterious `SIGSEGV (Address boundary error)`.

Replace it with opendir/readdir/closedir instead to mitigate this
problem.

Closes #122
dduan added a commit that referenced this issue Apr 3, 2020
On macOS 10.15.4, accessing data structure returned by `scandir`
occassionally returns a mysterious `SIGSEGV (Address boundary error)`.

Replace it with opendir/readdir/closedir instead to mitigate this
problem.

Closes #122
dduan added a commit that referenced this issue Apr 3, 2020
On macOS 10.15.4, accessing data structure returned by `scandir`
occassionally returns a mysterious `SIGSEGV (Address boundary error)`.

Replace it with opendir/readdir/closedir instead to mitigate this
problem.

Closes #122
@dduan dduan closed this as completed in #123 Apr 3, 2020
dduan added a commit that referenced this issue Apr 3, 2020
On macOS 10.15.4, accessing data structure returned by `scandir`
occassionally returns a mysterious `SIGSEGV (Address boundary error)`.

Replace it with opendir/readdir/closedir instead to mitigate this
problem.

Closes #122
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

Successfully merging a pull request may close this issue.

1 participant