Merge pull request MicrosoftDocs#4993 from MicrosoftDocs/main

7/25/2023 10:30 AM Publish

Author: PhilKang0704

docs/c-language/c-enumeration-declarations.md

@@ -103,7 +103,7 @@ enum BOOLEAN end_flag, match_flag; /* Two variables of type BOOLEAN */
 This declaration can also be specified as
 
 ```C
-enum BOOLEAN { false, true } end_flag, match_flag;\
+enum BOOLEAN { false, true } end_flag, match_flag;
 ```
 
 or as

docs/c-language/c-type-specifiers.md

@@ -55,7 +55,7 @@ The Microsoft C compiler also generates warnings for differences in sign. For ex
 
 ```C
 signed int *pi;
-unsigned int *pu
+unsigned int *pu;
 
 pi = pu;  /* Now generates warning */
 ```

docs/c-language/declarators-and-variable-declarations.md

@@ -67,7 +67,7 @@ int list[20]; // Declares an array of 20 int values named list
 char *cp;     // Declares a pointer to a char value
 double func( void ); // Declares a function named func, with no
                      // arguments, that returns a double value
-int *aptr[10] // Declares an array of 10 pointers
+int *aptr[10]; // Declares an array of 10 pointers
 ```
 
 **Microsoft Specific**

docs/c-language/extern-storage-class-specifier.md

@@ -49,7 +49,7 @@ void func(void)
 }
 ```
 
-In this example, the variable `i` is defined in Source1.c with an initial value of 1. An **`extern`** declaration in Source2.c is makes 'i' visible in that file.
+In this example, the variable `i` is defined in Source1.c with an initial value of 1. An **`extern`** declaration in Source2.c makes 'i' visible in that file.
 
 In the `func` function, the address of the global variable `i` is used to initialize the **`static`** pointer variable `external_i`. This works because the global variable has **`static`** lifetime, meaning its address does not change during program execution. Next, a variable `i` is defined within the scope of `func` as a local variable with initial value 16. This definition does not affect the value of the external-level `i`, which is hidden by the use of its name for the local variable. The value of the global `i` is now accessible only through the pointer `external_i`.
 

docs/c-runtime-library/stdin-stdout-stderr.md

@@ -1,20 +1,18 @@
 ---
-description: "Learn more about: stdin, stdout, stderr"
+description: "Learn more about the definitions of: stdin, stdout, stderr"
 title: "stdin, stdout, stderr"
-ms.date: "10/23/2018"
+ms.date: "7/24/2023"
 f1_keywords: ["CORECRT_WSTDIO/stdin", "CORECRT_WSTDIO/stderr", "CORECRT_WSTDIO/stdout", "stdin", "stderr", "stdout"]
 helpviewer_keywords: ["stdout function", "standard output stream", "standard error stream", "stdin function", "standard input stream", "stderr function"]
-ms.assetid: badd4735-596d-4498-857c-ec8b7e670e4c
 ---
 # `stdin`, `stdout`, `stderr`
 
 ## Syntax
 
 ```C
-FILE *stdin;
-FILE *stdout;
-FILE *stderr;
-#include <stdio.h>
+#define stdin  /* implementation defined */
+#define stdout /* implementation defined */
+#define stderr /* implementation defined */
 ```
 
 ## Remarks

docs/sanitizers/asan-debugger-integration.md

@@ -34,10 +34,21 @@ When you link the VCAsan library to your executable, users can enable it to gene
 
 `set ASAN_SAVE_DUMPS=MyFileName.dmp`
 
-The file must have a .dmp suffix to follow the Visual Studio IDE conventions.
+The file must have a `.dmp` extension to follow the Visual Studio IDE conventions. (Prior to 17.7)
 
 Here's what happens when a dump file is specified for `ASAN_SAVE_DUMPS`: If an error gets caught by the AddressSanitizer runtime, it saves a crash dump file that has the metadata associated with the error. The debugger in Visual Studio version 16.9 and later can parse the metadata that's saved in the dump file. You can set `ASAN_SAVE_DUMPS` on a per-test basis, store these binary artifacts, and then view them in the IDE with proper source indexing.
 
+Visual Studio version 17.7 and later supports the following:
+
+* Quoted strings are now handled correctly. In previous versions, for environments inside of Visual Studio or when using PowerShell, setting the environment variable to contain quotes or spaces would fail to create the expected dump file.
+
+* When the `.dmp` extension is explicitly specified (for example, `set ASAN_SAVE_DUMPS=MyDmp.dmp`), VCAsan uses it explicitly, and will not add an associated process ID to the dump file name. 
+
+* If a `.dmp` file already exists with the same name specified from the environment variable, VCAsan modifies the file name as follows:
+  * Appends a number to the filename in parentheses. For example, `Myfile (1).dmp`.
+  * If after several attempts appending a number in parentheses fails to generate a unique name, the file is saved to an `%APPLOCAL%` temporary path that VCAsan will print. For example, `C:\Users\~\AppData\Local\Temp\Dump.dmp`.
+  * If saving to a temporary path fails, a diagnostic error is displayed.
+
 ## See also
 
 [AddressSanitizer overview](./asan.md)\
@@ -47,3 +58,4 @@ Here's what happens when a dump file is specified for `ASAN_SAVE_DUMPS`: If an e
 [AddressSanitizer shadow bytes](./asan-shadow-bytes.md)\
 [AddressSanitizer cloud or distributed testing](./asan-offline-crash-dumps.md)\
 [AddressSanitizer error examples](./asan-error-examples.md)
+