UCRT中SIGABRT_COMPAT的存在原因及预期用途技术问询

Great question—this boils down to historical compatibility and accommodating cross-platform code quirks in the UCRT's signal emulation layer (since Windows doesn’t have native Unix-style signals like Linux does). Let’s break this down clearly:

Background: UCRT Signal Values vs. Unix Systems #

First, some context: The UCRT (Universal C Runtime) inherited signal numbering from its predecessor, the MSVCRT. In MSVCRT, SIGABRT was defined as 22, and this value stuck around in UCRT to maintain backward compatibility with legacy Windows applications that might have hardcoded this number.

On Unix-like systems (including your Ubuntu 18.04), SIGABRT is universally mapped to 6. This mismatch creates a headache when porting Unix code that relies on the numeric value of SIGABRT instead of the standard macro.

What’s SIGABRT_COMPAT’s Intended Purpose? #

The SIGABRT_COMPAT macro exists specifically to bridge this gap:

• It’s a UCRT-specific alias that maps to 6, matching the Unix value of SIGABRT.
• Its sole intended use is for legacy ported code that hardcodes the numeric value 6 for SIGABRT (instead of using the standard SIGABRT macro). If you have old Unix code that checks for 6 in signal handlers or calls raise(6), swapping those references with SIGABRT_COMPAT lets the code work on UCRT without a full rewrite.

Why Not Just Change UCRT’s SIGABRT to 6? #

Backward compatibility is non-negotiable here. Millions of existing Windows applications were built against MSVCRT where SIGABRT was 22. Changing the value in UCRT would break any code that hardcodes 22 for SIGABRT—a risk the UCRT team couldn’t take. Adding the compatibility macro was a safer way to support cross-platform code without breaking legacy software.

Recommendations for Developers #

• For new code: Never rely on the numeric value of signals. Always use standard macros like SIGABRT when calling raise() or checking signal values in handlers. This keeps your code portable across all C/C++ implementations.
• For porting code: Prioritize updating the code to use SIGABRT instead of SIGABRT_COMPAT. The latter is UCRT-specific, so using it will make your code less portable to other platforms. Only use SIGABRT_COMPAT if you’re maintaining legacy code that can’t be modified.

内容的提问来源于stack exchange，提问作者sbseltzer