Bug 232790

Summary:	Add "gcore" GDB command info to the "meaningful backtraces" doc
Product:	[OLD] Docs on www.gentoo.org	Reporter:	Jaak Ristioja <jaak>
Component:	Other documents	Assignee:	Gentoo Quality Assurance Team <qa>
Status:	RESOLVED OBSOLETE
Severity:	enhancement
Priority:	High
Version:	unspecified
Hardware:	All
OS:	Linux
URL:	http://www.gentoo.org/proj/en/qa/backtraces.xml
Whiteboard:
Package list:		Runtime testing required:	---

Description Jaak Ristioja 2008-07-23 21:15:57 UTC

Please add information about the "gcore" a.k.a "generate-core-file" GDB command into the "How to get meaningful backtraces in Gentoo" document. This might prove valuable in cases where the user needs to restart or shut it down (e.g. services which need to be up and running) a crashed program which is being debugged. Generating core dumps via GDB is good alternative to system-wide core dump generation settings and allows the user to debug the program at a later time.

Command reference: http://sourceware.org/gdb/current/onlinedocs/gdb_9.html#SEC80

Comment 1 nm (RETIRED) gentoo-dev

2008-07-23 21:49:12 UTC

Documents in /proj/ belong to that project -- in this case, QA. Reassigning.

Comment 2 Jaak Ristioja 2013-01-03 20:32:46 UTC

Here's an updated link to the documentation of the "gcore" command:

http://sourceware.org/gdb/current/onlinedocs/gdb/Core-File-Generation.html

Comment 3 nm (RETIRED) gentoo-dev

2018-01-21 01:51:34 UTC

everything's on the wiki nowadays. the qa team has already listed their preferred method of getting core dumps, but you're welcome to edit the backtraces wiki page to add the gcore command:

[1] https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces
[2] https://sourceware.org/gdb/onlinedocs/gdb/gcore-man.html