We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
core_locale
Version: 0.1.0 (development)
Steps to reproduce:
SPConfig.cfg
Expected behaviour:
Files and logs: SPConfig.cfg, SystemMessages.log and a link to the Crash Dump can be found inside this Gist.
SystemMessages.log
The text was updated successfully, but these errors were encountered:
I can't reproduce it on my system. What kind of "invalid" 'core_locale' did you use? Also a backtrace could be useful.
Sorry, something went wrong.
@theunknownxy
I used an inexistent one. I will try to reproduce it with latest build and provide a backtrace tomorrow.
EDIT: Done.
Here's a callstack (you'll still probably want to repro it yourself if you want to fix it):
I changed the core_locale to pc_cp, restarted the client, crash occured (read access violation).
pc_cp
The bug is here, I think it's trying to print a string that's not null-terminated:
ccd365b
This was the actual cause of the issue:
SPLog("Catalog file for the locale '%s' was not found. (domain='%s')", - domainName.c_str()); + currentLocaleRegion.c_str(), domainName.c_str());
yvt
No branches or pull requests
Version: 0.1.0 (development)
Steps to reproduce:
SPConfig.cfg
to have an invalidcore_locale
(one that can't be found or does not exist)Expected behaviour:
core_locale
to an valid one.Files and logs:
SPConfig.cfg
,SystemMessages.log
and a link to the Crash Dump can be found inside this Gist.The text was updated successfully, but these errors were encountered: