From a1af0a707ea51fe8f88b408b38be5f590fe9d6d5 Mon Sep 17 00:00:00 2001 From: Sebastian Solnica Date: Mon, 1 Jan 2024 20:16:59 +0100 Subject: [PATCH] Updated links to TTD guide --- guides/diagnosing-dotnet-apps.md | 2 +- guides/diagnosing-native-windows-apps.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/guides/diagnosing-dotnet-apps.md b/guides/diagnosing-dotnet-apps.md index 8f5c563..f19d934 100644 --- a/guides/diagnosing-dotnet-apps.md +++ b/guides/diagnosing-dotnet-apps.md @@ -199,7 +199,7 @@ Stopping the trace. This may take up to minutes depending on the application bei ### Using Time Travel Debugging (TTD) -Time Travel Debugging is an excellent way of troubleshooting errors and exceptions. We can step through the code causing the problems at our own pace. I describe TTD in [the WinDbg usage guide](using-windbg#time-travel-debugging-ttd). It is my preferred way of debugging issues in applications and I highly recommend giving it a try. +Time Travel Debugging is an excellent way of troubleshooting errors and exceptions. We can step through the code causing the problems at our own pace. I describe TTD in [the WinDbg usage guide](/guides/using-windbg#time-travel-debugging-ttd). It is my preferred way of debugging issues in applications and I highly recommend giving it a try. ### Collecting a memory dump diff --git a/guides/diagnosing-native-windows-apps.md b/guides/diagnosing-native-windows-apps.md index 8be287c..3fee2a1 100644 --- a/guides/diagnosing-native-windows-apps.md +++ b/guides/diagnosing-native-windows-apps.md @@ -38,7 +38,7 @@ title: Diagnosing native Windows applications ### Using Time Travel Debugging (TTD) or live debugging -Time Travel Debugging is an excellent way of troubleshooting errors and exceptions. We can step through the code causing the problems at our own pace. I describe TTD in [the WinDbg usage guide](using-windbg#time-travel-debugging-ttd). It is my preferred way of debugging issues in applications and I highly recommend giving it a try. +Time Travel Debugging is an excellent way of troubleshooting errors and exceptions. We can step through the code causing the problems at our own pace. I describe TTD in [the WinDbg usage guide](/guides/using-windbg#time-travel-debugging-ttd). It is my preferred way of debugging issues in applications and I highly recommend giving it a try. #### Break on a specific exception event