Open AntiBlueQuirk opened 7 years ago
Has the referenced commit fixed this issue?
I think it should, and I forgot to close this issue... Not very confident though.
This issue was actually reported to wxWidgets by someone but that ticket is closed as Not Repro. Think over again I decide to change my machine to en-us locale and then rebuild wxWidgets. I remember that it worked
Using wxLocale features seems to cause problems. wxWidgets fails while it is calling wxLocale::GetInfo(int, int), or if you call it manually. (The attached program shows the second case.) Since wxWidgets calls this all over the place, the program quickly crashes if you do anything significant after initializing a wxLocale object.
The following error is thrown from wxWidgets during the call:
To be perfectly honest, I'm not actually sure if this is a problem in wxWidgets, wxGo, or some weird interaction between them and Go. I traced through the program in gdb, and nothing seems to call setlocale() directly after initializing the wxLocale, but I'm not very sure.
Here is an example backtrace from a crash while creating a bitmap (I tried to clean it up a little.):
My environment is Windows 10, with wxGo compiled with a Windows native Go installation, and GCC from MSYS2 MinGW. Everything else I've tried up to this point has worked fine.
(The attached program is named .txt so GitHub will accept the upload.) wxLocaleTest.go.txt