Skip to content

[Run issue]: TsIRTInterTrack Segmentation Fault #16

Discussion options

You must be logged in to vote

Seems to be an issue only with specific seed numbers. Can brute force with low history counts to determine the faulty seed numbers and then after that it seems to be fine as long as you avoid these seeds.

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Answer selected by Gavin-Pikes
Comment options

You must be logged in to vote
1 reply
@Gavin-Pikes
Comment options

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants