diff options
| author | Russ Cox <rsc@golang.org> | 2020-03-14 09:44:01 -0400 |
|---|---|---|
| committer | Russ Cox <rsc@golang.org> | 2020-03-17 20:58:41 +0000 |
| commit | faf1e2da2d911edc717993e8edb24fe88f99b2b5 (patch) | |
| tree | 3b7d10f5f95b7bc9ca63d0591bd120b8d8f015b6 /content/debugging-go-code-status-report.article | |
| parent | af5018f64e406aaa646dae066f28de57321ea5ce (diff) | |
content: write real summary for each article
The pre-Markdown blog invented a summary by copying
the first paragraph of text. Often this was nonsense or
at least useless.
The new Markdown-enabled present format adds an
explicit Summary line. The conversion populated these
with the same first paragraph that the old format would
have used implicitly.
This commit rewrites them all to be proper short summaries.
Change-Id: If2e1e101b95558d7ecd53c613f733a7f89c680f1
Reviewed-on: https://go-review.googlesource.com/c/blog/+/223598
Run-TryBot: Russ Cox <rsc@golang.org>
Reviewed-by: Andrew Bonventre <andybons@golang.org>
Diffstat (limited to 'content/debugging-go-code-status-report.article')
| -rw-r--r-- | content/debugging-go-code-status-report.article | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/debugging-go-code-status-report.article b/content/debugging-go-code-status-report.article index e253a10..7881bc5 100644 --- a/content/debugging-go-code-status-report.article +++ b/content/debugging-go-code-status-report.article @@ -1,7 +1,7 @@ # Debugging Go code (a status report) 2 Nov 2010 Tags: debug, gdb -Summary: When it comes to debugging, nothing beats a few strategic print statements to inspect variables or a well-placed panic to obtain a stack trace. However, sometimes you’re missing either the patience or the source code, and in those cases a good debugger can be invaluable. That's why over the past few releases we have been improving the support in Go’s gc linker (6l, 8l) for GDB, the GNU debugger. +Summary: What works and what doesn't when debugging Go programs with GDB. Luuk van Dijk |