Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

doc/gdb: mention GOTRACEBACK=crash in more places #6877

Closed
gopherbot opened this issue Dec 3, 2013 · 4 comments
Closed

doc/gdb: mention GOTRACEBACK=crash in more places #6877

gopherbot opened this issue Dec 3, 2013 · 4 comments

Comments

@gopherbot
Copy link

by aaron.blohowiak:

The go gdb documentation mentions that gdb can be used against a live process or a core
dump, but the method to create a dump is not discussed here. please mention
GOTRACEBACK=crash in the go gdb docs.  It might also be useful to mention in
runtime/debug as it is a vital debugging tool.
@rsc
Copy link
Contributor

rsc commented Dec 4, 2013

Comment 1:

Labels changed: added release-none, removed go1.3maybe.

@rsc
Copy link
Contributor

rsc commented Dec 4, 2013

Comment 2:

Labels changed: added repo-main.

@robpike
Copy link
Contributor

robpike commented Mar 5, 2014

Comment 3:

Labels changed: added gdb.

@bradfitz bradfitz removed the new label Dec 18, 2014
@rsc rsc removed the gdb label Apr 10, 2015
@rsc rsc added this to the Unplanned milestone Apr 10, 2015
@gopherbot
Copy link
Author

CL https://golang.org/cl/34960 mentions this issue.

@golang golang locked and limited conversation to collaborators Jan 13, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants