Skip to content

Commit 474bcda

Browse files
authored
remove locale
1 parent 9375d11 commit 474bcda

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/debugger/how-can-i-find-out-if-my-pointers-corrupt-a-memory-address-q.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ ms.workload:
3030

3131
#### Check for heap corruption
3232

33-
- Most memory corruption is actually due to heap corruption. Try using the Global Flags Utility (gflags.exe) or pageheap.exe. See [https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/gflags-and-pageheap](/windows-hardware/drivers/debugger/gflags-and-pageheap).
33+
- Most memory corruption is actually due to heap corruption. Try using the Global Flags Utility (gflags.exe) or pageheap.exe. See [https://docs.microsoft.com/windows-hardware/drivers/debugger/gflags-and-pageheap](/windows-hardware/drivers/debugger/gflags-and-pageheap).
3434

3535
#### To find where the memory address is modified
3636

0 commit comments

Comments
 (0)