-
Notifications
You must be signed in to change notification settings - Fork 41
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
Assertion nation_check(pplayer->nation) failed #2195
Comments
jwrober
added
bug
Something isn't working
Untriaged
This issue or PR needs triaging
labels
Feb 8, 2024
The mention of this issue from the LTT-LTX pull request was an mistake. Please ignore, I can't remove the reference. |
Stack trace:
|
lmoureaux
added
gui
This issue requires changes to the user interface
and removed
Untriaged
This issue or PR needs triaging
labels
Mar 17, 2024
lmoureaux
added a commit
to lmoureaux/freeciv21
that referenced
this issue
Mar 17, 2024
Since it's used everywhere in the client code to determine the current player, keeping it set to a dangling value triggers various assertions. Closes longturn#2195.
lmoureaux
added a commit
that referenced
this issue
Mar 24, 2024
Since it's used everywhere in the client code to determine the current player, keeping it set to a dangling value triggers various assertions. Closes #2195.
lmoureaux
added a commit
that referenced
this issue
Mar 30, 2024
Since it's used everywhere in the client code to determine the current player, keeping it set to a dangling value triggers various assertions. Closes #2195.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Two assertions
nation.cpp:422 - Assertion nation_check(pplayer->nation) failed
nation.cpp:466 - Assertion nullptr != pnation failed
To Reproduce
Steps to reproduce the behavior:
Expected behavior
No error
Screenshots
N/A
Platform and version (please complete the following information):
Additional context
Not sure it matters, but came up while testing map gen recipes.
The text was updated successfully, but these errors were encountered: