diff options
| -rw-r--r-- | doc/C/evolution-faq.sgml | 65 | ||||
| -rw-r--r-- | doc/ChangeLog | 10 | ||||
| -rw-r--r-- | help/C/evolution-faq.sgml | 65 | ||||
| -rw-r--r-- | help/ChangeLog | 10 |
4 files changed, 142 insertions, 8 deletions
diff --git a/doc/C/evolution-faq.sgml b/doc/C/evolution-faq.sgml index 0dac339f0a..92afbf1087 100644 --- a/doc/C/evolution-faq.sgml +++ b/doc/C/evolution-faq.sgml @@ -1,6 +1,5 @@ -<!-- <!DOCTYPE appendix PUBLIC "-//GNOME//DTD DocBook PNG Variant V1.1//EN"> ---> + <appendix id="evolution-faq"> <title>Frequently Asked Questions About Ximian Evolution</title> <para> @@ -312,7 +311,7 @@ <!-- Section: Getting and compiling --> - <sect1 id="get-and-compile"> + <sect1 id="faq-get-and-compile"> <title> Getting and Compiling Evolution </title> @@ -908,9 +907,69 @@ bt </para> </answer> </qandaentry> + <qandaentry> + <question> + <para> + A component of evolution crashed, but since the rest of + evolution stayed up, I couldn't use bug-buddy to get a + stack trace. How can I use gdb to get a stack trace of + the component? + </para> + </question> + <answer> + <para> + To trace a failing component (in this example, evolution-mail): + <orderedlist numeration="arabic"> + <listitem> + <para> + Open two terminals. + </para> + </listitem> + <listitem> + <para> + In one, type <command>gdb evolution-mail</command> + . Replace "evolution-mail" with the name of the + component that is crashing: evolution-addresbook, + evolution-calendar, etc.) + </para> + </listitem> + <listitem> + <para> + Once gdb starts, type <userinput>r</userinput> and + hit enter. Give it a few seconds, to make sure it + starts up completely. + </para> + </listitem> + <listitem> + <para> + In the second terminal, type + <command>evolution</command>. Do whatever you did + to cause the crash in the component you used in + step two. + </para> + </listitem> + <listitem> + <para> + When the crash occurs, type 'bt' in the first + terminal. + </para> + </listitem> + + <listitem> + <para> + Cut and paste the output into your bug report. + </para> + </listitem> + </orderedlist> + </para> + </answer> + </qandaentry> </qandaset> </sect1> </appendix> <!-- Local Variables: --> <!-- indent-tabs-mode:nil --> <!-- End: --> + + + diff --git a/doc/ChangeLog b/doc/ChangeLog index e038835bb3..572defc7ab 100644 --- a/doc/ChangeLog +++ b/doc/ChangeLog @@ -1,10 +1,18 @@ +2001-07-12 Aaron Weber <aaron@ximian.com> + + * C/evolution-faq.sgml: + +2001-07-12 Aaron Weber <aaron@ximian.com> + + * C/evolution-faq.sgml: Added "get bt for component-only crash" qandaentry. + 2001-07-10 Peter Williams <peterw@ximian.com> * */Makefile.am (dist-hook): Clean up make dist. 2001-07-11 Aaron Weber <aaron@ximian.com> - * C/evolution.sgml: validation on usage-mainwindow and usage-contact. + * C/evolution.sgml: validation on usage-mainwindow and usage-contact. 2001-07-11 Kevin Breit <battery841@mediaone.net> diff --git a/help/C/evolution-faq.sgml b/help/C/evolution-faq.sgml index 0dac339f0a..92afbf1087 100644 --- a/help/C/evolution-faq.sgml +++ b/help/C/evolution-faq.sgml @@ -1,6 +1,5 @@ -<!-- <!DOCTYPE appendix PUBLIC "-//GNOME//DTD DocBook PNG Variant V1.1//EN"> ---> + <appendix id="evolution-faq"> <title>Frequently Asked Questions About Ximian Evolution</title> <para> @@ -312,7 +311,7 @@ <!-- Section: Getting and compiling --> - <sect1 id="get-and-compile"> + <sect1 id="faq-get-and-compile"> <title> Getting and Compiling Evolution </title> @@ -908,9 +907,69 @@ bt </para> </answer> </qandaentry> + <qandaentry> + <question> + <para> + A component of evolution crashed, but since the rest of + evolution stayed up, I couldn't use bug-buddy to get a + stack trace. How can I use gdb to get a stack trace of + the component? + </para> + </question> + <answer> + <para> + To trace a failing component (in this example, evolution-mail): + <orderedlist numeration="arabic"> + <listitem> + <para> + Open two terminals. + </para> + </listitem> + <listitem> + <para> + In one, type <command>gdb evolution-mail</command> + . Replace "evolution-mail" with the name of the + component that is crashing: evolution-addresbook, + evolution-calendar, etc.) + </para> + </listitem> + <listitem> + <para> + Once gdb starts, type <userinput>r</userinput> and + hit enter. Give it a few seconds, to make sure it + starts up completely. + </para> + </listitem> + <listitem> + <para> + In the second terminal, type + <command>evolution</command>. Do whatever you did + to cause the crash in the component you used in + step two. + </para> + </listitem> + <listitem> + <para> + When the crash occurs, type 'bt' in the first + terminal. + </para> + </listitem> + + <listitem> + <para> + Cut and paste the output into your bug report. + </para> + </listitem> + </orderedlist> + </para> + </answer> + </qandaentry> </qandaset> </sect1> </appendix> <!-- Local Variables: --> <!-- indent-tabs-mode:nil --> <!-- End: --> + + + diff --git a/help/ChangeLog b/help/ChangeLog index e038835bb3..572defc7ab 100644 --- a/help/ChangeLog +++ b/help/ChangeLog @@ -1,10 +1,18 @@ +2001-07-12 Aaron Weber <aaron@ximian.com> + + * C/evolution-faq.sgml: + +2001-07-12 Aaron Weber <aaron@ximian.com> + + * C/evolution-faq.sgml: Added "get bt for component-only crash" qandaentry. + 2001-07-10 Peter Williams <peterw@ximian.com> * */Makefile.am (dist-hook): Clean up make dist. 2001-07-11 Aaron Weber <aaron@ximian.com> - * C/evolution.sgml: validation on usage-mainwindow and usage-contact. + * C/evolution.sgml: validation on usage-mainwindow and usage-contact. 2001-07-11 Kevin Breit <battery841@mediaone.net> |