-
-
Notifications
You must be signed in to change notification settings - Fork 988
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
Crash with debug command :unit advances=yes
#7402
Comments
Looks like Seems a good first issue, it's a self-contained C++ function doing standard C++ string handling. Reading PR #6688 would explain where the commands are being typed, and what this code is used for. |
Confirmed on both master and 1.16 - log just makes a mention of |
Oh, interesting. It's good to have a fix for the other issue, but that bug isn't the one that sevu posted the stack trace for; the one that sevu found is only on 1.17 ( Ah, the stack trace is for missing the space, so it's As the PR is already open, probably repurpose this to be the |
Odd. Against master I've tried |
I didn't replicate sevu's bug until now, previously I just looked at the stack trace he provided. Edit: the rest of the comment is #7412, not #7402. That assert only triggers if Wesnoth is built with Adding a CMake and SCons option for |
:unit advances=yes
The fact that it's an assert with |
:unit advances=yes
cause the game to crash.(correct would be
unit advances=3
times, i.e. a number is expected, string causes a crash) The correct behaviour would be to just ignore the command.Build c9eae7c
The text was updated successfully, but these errors were encountered: