6

We currently face the problem that an external component (we unfortunately don't know which one) that is loaded when using the Windows file open/save dialog one some systems changes the locale of the process, probably by making the call setlocale(LC_ALL, "").

This messes up our application, because it relies on the standard locale being set (which is not changed by any of our own components during runtime).

So we need to make sure that either setlocale() never has any effect when called within the process, or we need to detect whenever this function is called and then reset the locale to the default "C" locale.

Is there a way to achieve either of these goals?

Niall
  • 30,036
  • 10
  • 99
  • 142
floele
  • 3,668
  • 4
  • 35
  • 51
  • 1
    You can put a breakpoint on library functions - see https://stackoverflow.com/questions/3080624/debug-break-on-win32-api-functions – sashoalm Sep 29 '14 at 14:06
  • @sashoalm Thanks, but unfortunately we cannot debug this issue because it doesn't happen on any development PC. Even if it did and we knew the component, it wouldn't really help much protecting the process against such changes. – floele Sep 29 '14 at 14:08
  • Try using a trampoline then - https://stackoverflow.com/questions/189725/what-is-a-trampoline-function – sashoalm Sep 29 '14 at 14:57
  • @sashoalm How would that help? – floele Sep 29 '14 at 15:08
  • it is possible to intercept function calls, but it is not a trivial task - [here](https://software.intel.com/en-us/articles/intercepting-system-api-calls) is a good walkthrough. But this way you still need at least to check your components use dll version of CRT. – dewaffled Sep 29 '14 at 16:06

1 Answers1

2

This is not really a direct answer to the question, but a solution for the underlying problem. It turned out that a recent update to iCloud caused this issue, see this post for example:

https://discussions.apple.com/thread/5356698

So there are two solutions, one renaming the ShellStreams.dll, the other one is uninstalling iClould completely (if it's not used anyway).

An actual protection that could be used is making setlocale() just thread-global instead of process-global:

_configthreadlocale(_ENABLE_PER_THREAD_LOCALE)

It worked in a simple test application of ours, but not in the real world case (so not an actual solution for us).

The most reliable way to solve this problem if you cannot uninstall iCloud is to use the "_l"-functions, which work using a specific locale like this:

_locale_t localeInfo = _create_locale(LC_NUMERIC, "C");
_sprintf_l(string, format, localeInfo, number);
_free_locale(localeInfo);
floele
  • 3,668
  • 4
  • 35
  • 51