diff options
| author | Jan Vorlicek <janvorli@microsoft.com> | 2019-03-07 16:10:55 +0100 |
|---|---|---|
| committer | Jan Vorlicek <janvorli@microsoft.com> | 2019-03-07 16:10:55 +0100 |
| commit | 638b1c1eeaf49282dcb036376ae6e35a7b62aee3 (patch) | |
| tree | 026193bd7fda2f750a3571659b40ea672c4973fb /src/pal/src/init | |
| parent | 98cd595b35ced3adb6efe0c667f5160f21067e0b (diff) | |
| download | coreclr-638b1c1eeaf49282dcb036376ae6e35a7b62aee3.tar.gz coreclr-638b1c1eeaf49282dcb036376ae6e35a7b62aee3.tar.bz2 coreclr-638b1c1eeaf49282dcb036376ae6e35a7b62aee3.zip | |
Remove init_count zeroing from PAL cleanup
Setting the init_count to 0 in the PALCommonCleanup was causing
intermittent crashes in the GC stress C tests on Linux with
SIGILL. The reason is that the signal handlers do nothing and call a
previous handler in case the PAL is not initialized, which is indicated
by the init_count being zero.
To fix that issue, I have removed the init_count zeroing at process
exit, since the PAL and runtime is still capable of handling the
signals.
Diffstat (limited to 'src/pal/src/init')
| -rw-r--r-- | src/pal/src/init/pal.cpp | 3 |
1 files changed, 0 insertions, 3 deletions
diff --git a/src/pal/src/init/pal.cpp b/src/pal/src/init/pal.cpp index f6bbd6a82c..81504061d3 100644 --- a/src/pal/src/init/pal.cpp +++ b/src/pal/src/init/pal.cpp @@ -1042,9 +1042,6 @@ PALCommonCleanup() PROCDumpThreadList(); #endif } - - // Mark that the PAL is uninitialized - init_count = 0; } BOOL PALIsShuttingDown() |