From faf1e2da2d911edc717993e8edb24fe88f99b2b5 Mon Sep 17 00:00:00 2001 From: Russ Cox Date: Sat, 14 Mar 2020 09:44:01 -0400 Subject: 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 Reviewed-by: Andrew Bonventre --- content/debugging-go-code-status-report.article | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'content/debugging-go-code-status-report.article') 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 -- cgit v1.2.3