From 921ed069c341a521d817fc21d7b9ede22017a0df Mon Sep 17 00:00:00 2001 From: Joe Marcus Clarke Date: Sat, 14 Oct 2006 17:19:11 +0000 Subject: [PATCH] Add a reference to the GNOME back trace debugging guide to the Development Branch FAQ and the debugging pages. Suggested by: P.U.Kruppa --- en/gnome/docs/bugging.sgml | 12 +++++++++--- en/gnome/docs/develfaq.sgml | 4 +++- 2 files changed, 12 insertions(+), 4 deletions(-) diff --git a/en/gnome/docs/bugging.sgml b/en/gnome/docs/bugging.sgml index 7895028ac9..fd39f51bb4 100644 --- a/en/gnome/docs/bugging.sgml +++ b/en/gnome/docs/bugging.sgml @@ -1,6 +1,6 @@ - + ]> @@ -61,8 +61,14 @@ attachments to the mailing list, because attachments sent to FreeBSD mailing lists are usually discarded by the mailing list software. -
  • If a program produces a core dump, provide a stack - trace. +
  • If a program produces a core dump, provide a + back trace. Back traces are only useful if the + application (and possibly its dependencies) are + compiled with debugging symbols. See these + instructions + for more information on obtaining useful back + traces.
  • If an application produces unexpected behavior, provide a clear and detailed description, including a description of the behavior that you were expecting. diff --git a/en/gnome/docs/develfaq.sgml b/en/gnome/docs/develfaq.sgml index e5461a0fa5..0196aa95ed 100644 --- a/en/gnome/docs/develfaq.sgml +++ b/en/gnome/docs/develfaq.sgml @@ -1,6 +1,6 @@ - + ]> @@ -92,6 +92,8 @@ CFLAGS= -O -g -pipe STRIP= +

    GNOME has an excellent guide for getting + useful back traces.