Fix heartbeat pthread_create segmentation fault #142
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Can confirm that this fixes the issue for me too. Why does it fix it? Is the problem that the heartbeat_c cfunction goes out of scope and is destroyed before being called by the new thread? |
stevengj
added a commit
that referenced
this pull request
Feb 4, 2014
Fix heartbeat pthread_create segmentation fault
|
It seems that this issue was due to my Arch linux system being using LLVM v3.4, which also caused other segfaults, see JuliaLang/julia#5696 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In recent Julia builds (Version 0.3.0-prerelease+1379 Commit 00760bd*), at least in Arch Linux, IJulia kernel segfaults in the heartbeat pthread creation.
I found that moving the heartbeat_c cfunction object out of the start_heartbeat function solves the issue.
(Probably this is the issue also mentioned by @aelg in #138)