From 4601eae6baed9c4bc6e38f035d1b6a20bb7ebbf7 Mon Sep 17 00:00:00 2001 From: Alberto Donizetti Date: Mon, 9 Jan 2017 19:11:58 +0100 Subject: [PATCH] doc/gdb: mention GOTRACEBACK=crash Also fix a couple of other errors. Fixes #6877 Change-Id: I94c81c5847cc7b0adab19418e71687bc2ee7fe94 Reviewed-on: https://go-review.googlesource.com/34960 Reviewed-by: Ian Lance Taylor --- doc/debugging_with_gdb.html | 17 ++++++++++++++--- 1 file changed, 14 insertions(+), 3 deletions(-) diff --git a/doc/debugging_with_gdb.html b/doc/debugging_with_gdb.html index 52a6e76723..f0e65ea291 100644 --- a/doc/debugging_with_gdb.html +++ b/doc/debugging_with_gdb.html @@ -4,7 +4,8 @@ }-->

-This applies to the gc toolchain. Gccgo has native gdb support. +This applies to the standard toolchain (the gc Go +compiler and tools). Gccgo has native gdb support. Besides this overview you might want to consult the GDB manual.

@@ -49,6 +50,14 @@ when debugging, pass the flags -gcflags "-N -l" to the debugged.

+

+If you want to use gdb to inspect a core dump, you can trigger a dump +on a program crash, on systems that permit it, by setting +GOTRACEBACK=crash in the environment (see the + runtime package +documentation for more info). +

+

Common Operations