You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some users have reported running into a segfault after commit e21f25992369d39c9abb920259dd8fef3f30d973 (see issue #2). The maintainers cannot reproduce this issue, therefore, this needs to be observed whether it occurs for more users in the future. Since the issue was most likely introduced by the correction of the thread handing, we a special branch nothreadfix was created, which is similar to the current master, but does not have the thread handling corrections.
When using this branch, the program will therefore still report terminate called without an active exception on termination, which can be ignored.
The text was updated successfully, but these errors were encountered:
OK - so the error must be somewhere in the communicator. As already mentioned, since we cannot reproduce the bug, you need to perform manual debugging on your machine and figure out where and why this error is thrown. We already tried to investigate what happens in line 409 by adding some cout commands printing the ContainerSize and msg_type_container_.size() - I would recommend revisiting this idea. Particularly, if there is not output shown, the failure cannot be caused by line 409, since the cout statements are executed before. If this is the case, you need to trace down the line that actually causes the segfault.
The most promising way to find the problem is to deactivate the changes introduced after commit e21f25992369d39c9abb920259dd8fef3f30d973 step by step and see which change causes the problem on your machine.
The compare function of github might help here: e21f259...versions/nothreadfix
Some users have reported running into a segfault after commit
e21f25992369d39c9abb920259dd8fef3f30d973
(see issue #2). The maintainers cannot reproduce this issue, therefore, this needs to be observed whether it occurs for more users in the future. Since the issue was most likely introduced by the correction of the thread handing, we a special branch nothreadfix was created, which is similar to the current master, but does not have the thread handling corrections.When using this branch, the program will therefore still report
terminate called without an active exception
on termination, which can be ignored.The text was updated successfully, but these errors were encountered: