Skip to content

Commit 4fd7f86

Browse files
authored
Merge pull request #5819 from MicrosoftDocs/repo_sync_working_branch
Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/visualstudio-docs (branch master)
2 parents a0d8988 + 11c3ef3 commit 4fd7f86

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

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

Lines changed: 2 additions & 2 deletions
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 [http://support.microsoft.com/default.aspx?scid=kb;en-us;286470](http://support.microsoft.com/default.aspx?scid=kb;en-us;286470).
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

@@ -40,4 +40,4 @@ ms.workload:
4040

4141
## See also
4242
- [Debugging Native Code FAQs](../debugger/debugging-native-code-faqs.md)
43-
- [Debugging Native Code](../debugger/debugging-native-code.md)
43+
- [Debugging Native Code](../debugger/debugging-native-code.md)

0 commit comments

Comments
 (0)