Skip to content

Commit 16a0ab3

Browse files
authored
Fix link (dotnet#59200)
1 parent 5588f94 commit 16a0ab3

File tree

1 file changed

+1
-1
lines changed
  • docs/design/coreclr/profiling/davbr-blog-archive

1 file changed

+1
-1
lines changed

docs/design/coreclr/profiling/davbr-blog-archive/Attach.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
*This blog post originally appeared on David Broman's blog on 11/4/2009*
22

3-
***[Update 5/30/19]: The archived content below refers to an Attach mechanism that only worked on desktop, not on .Net Core. Please see [Profiler Attach on CoreCLR](../Profiler Attach on Coreclr.md) for profiler attach on CoreCLR***
3+
***[Update 5/30/19]: The archived content below refers to an Attach mechanism that only worked on desktop, not on .Net Core. Please see [Profiler Attach on CoreCLR](../Profiler%20Attach%20on%20CoreCLR.md) for profiler attach on CoreCLR***
44

55

66
Profiler attach is a feature that allows you to attach a profiler to an already running process. The usefulness of this is fairly obvious to anyone who's ever attached a debugger to a running-process: It's helpful when diagnosing hard-to-reproduce problems, and particularly useful when encountering issues in production.

0 commit comments

Comments
 (0)