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

Segfaults reported after commit e21f25992369d39c9abb920259dd8fef3f30d973 #11

Open
patriksc opened this issue Jan 8, 2022 · 4 comments
Assignees
Labels
under observation This issue need observation to determine its significance

Comments

@patriksc
Copy link
Collaborator

patriksc commented Jan 8, 2022

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.

@patriksc patriksc added the under observation This issue need observation to determine its significance label Jan 8, 2022
@patriksc patriksc self-assigned this Jan 8, 2022
@RoZhong
Copy link

RoZhong commented Jan 12, 2022

Sorry I didn't experiment until today. The answer is below ,it is still error

选区_075
选区_078
选区_079

@RoZhong
Copy link

RoZhong commented Jan 12, 2022

一些用户报告在提交后e21f25992369d39c9abb920259dd8fef3f30d973遇到了段错误(参见问题#2)。维护者无法重现此问题,因此需要观察未来是否会出现更多用户。由于问题很可能是由线程处理的更正引入的,因此我们创建了一个特殊的分支nothreadfix,它与当前的 master 类似,但没有线程处理的更正。

因此,当使用此分支时,程序仍会报告terminate called without an active exception终止,可以忽略。

but this time It runs to "wait for back-end response", I looked at the last one and it didn't run to this step

@patriksc
Copy link
Collaborator Author

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.

@patriksc
Copy link
Collaborator Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
under observation This issue need observation to determine its significance
Projects
None yet
Development

No branches or pull requests

2 participants