Please enable JavaScript to use regex101
/
^
r
e
g
e
x
[
\
-
_
]
?
1
0
1
$
/
i
Reg
ular
Ex
pressions
101
Upgrade to Pro
Enterprise
Regular Expression
/
(<*\s*[^>]*)(href=)(.?)(\/[^\/])
/
gm
Input 1
New
<div id="blog"><div id="content"> <div id="content"> <div class="Article" data-slug="/blog/execution-traces-2024"> <h1 class="small"><a href="//go.dev/blog/">The Go Blog</a></h1> <h1>More powerful Go execution traces</h1> <p class="author"> Michael Knyszek<br> 14 March 2024 </p> <p>The <a href="//go.dev/pkg/runtime/trace">runtime/trace</a> package contains a powerful tool for understanding and troubleshooting Go programs. The functionality within allows one to produce a trace of each goroutine’s execution over some time period. With the <a href="//go.dev/pkg/cmd/trace"><code>go tool trace</code> command</a> (or the excellent open source <a href="https://gotraceui.dev/" rel="noreferrer" target="_blank">gotraceui tool</a>), one may then visualize and explore the data within these traces.</p> <p>The magic of a trace is that it can easily reveal things about a program that are hard to see in other ways. For example