additions

Original commit message from CVS:
additions

docs/faq/troubleshooting.xml

@@ -2,6 +2,74 @@
   <title id="title-troubleshooting">Troubleshooting GStreamer</title>
   <qandaset>
 
+    <qandaentry>
+      <question id="troubleshooting-segfault">
+        <para>
+The GStreamer application I used stops with a segmentation fault.  What can
+I do ?
+        </para>
+      </question>
+
+      <answer>
+        <para>
+There are two things you can do.  If you compiled GStreamer with specific
+optimization compilation flags, you should try recompiling GStreamer,
+the application and the plug-ins without any optimization flags.  This allows
+you to verify if the problem is due to optimization or due to bad code.
+Second, it will also allow you to provide a reasonable backtrace in case
+the segmentation fault still occurs.
+        </para>
+        <para>
+The second thing you can do is look at the backtrace to get an idea of where
+things are going wrong, or give us an idea of what is going wrong.
+To provide a backtrace, you should
+<orderedlist>
+<listitem>
+  run the application in gdb by starting it with
+  <programlisting>
+    gdb (gst-application)
+  </programlisting>
+  (If the application is in a source tree instead of installed on the system,
+  you might want to put "libtool" before "gdb")
+</listitem>
+<listitem>
+  Pass on the command line arguments to the application by typing
+  <programlisting>
+    set args (the arguments to the application)
+  </programlisting>
+  at the (gdb) prompt
+</listitem>
+<listitem>
+  Type "run" at the (gdb) prompt and wait for the application to
+  segfault.  The application will run a lot slower, however.
+</listitem>
+<listitem>
+  After the segfault, type "bt" to get a backtrace.  This is a stack of
+  function calls detailing the path from main () to where the code is
+  currently at.
+</listitem>
+<listitem>
+  If the application you're trying to debug contains threads, it is also
+  useful to do
+  <programlisting>
+    info threads
+  </programlisting>
+  and get backtraces of all of the threads involved, by switching to
+  a different thread using "thread (number)" and then again requesting
+  a backtrace using "bt".
+</listitem>
+<listitem>
+  <para>
+  If you can't or don't want to work out the problem yourself, a copy and paste
+  of all this information should be included in your 
+  <link linkend="using-bugs-where">bug report</link>.
+  </para>
+</listitem>
+</orderedlist>
+        </para>
+      </answer>
+    </qandaentry>
+
     <qandaentry>
       <question id="troubleshooting-wiki">
         <para>
@@ -19,5 +87,6 @@ someone else.
         </para>
       </answer>
     </qandaentry>
+
   </qandaset>
 </sect1>

docs/faq/using.xml

@@ -31,7 +31,7 @@ plugin browser available, gst-inspect-gui.
     </qandaentry>
 
     <qandaentry>
-      <question id="using-bugs">
+      <question id="using-bugs-where">
         <para>Where should I report bugs ?</para>
       </question>
 
@@ -45,6 +45,16 @@ Bugzilla requires you to make an account here, which might seem cumbersome,
 but allows us to at least have a chance at contacting you for further
 information, as we will most likely have to.
         </para>
+      </answer>
+    </qandaentry>
+
+
+    <qandaentry>
+      <question id="using-bugs-how">
+        <para>How should I report bugs ?</para>
+      </question>
+
+      <answer>
         <para>
 When doing a bug report, you should at least describe
 <itemizedlist>
@@ -55,7 +65,7 @@ how you installed GStreamer (from cvs, source, packages, which ?)</listitem>
 </itemizedlist>
         </para>
         <para>
-If you're new to GStreamer, it also is useful for us if you attach output of
+It also is useful for us if you attach output of
 the gst-feedback command to your bug report.
 If you're having problem with a specific application (either one of ours,
 somebody else's, or your own), please also provide a log of gst-mask by
@@ -65,7 +75,12 @@ myapp --gst-mask=-1 > mask.log 2>&amp;1
 gzip mask.log
 </programlisting>
 (interrupting the program if it doesn't stop by itself)
-and attach mask.log.gz to your bug report
+and attach mask.log.gz to your bug report.
+        </para>
+        <para>
+If the application you are having problems with is segfaulting, then
+provide us with the necessary gdb output.  See
+<xref linkend="troubleshooting-segfault" endterm="troubleshooting-segfault"/>
         </para>
       </answer>
     </qandaentry>