Ticket #836: mythdocsgdbrealtime2.diff

docs/mythtv-HOWTO.sgml

@@ -5225 +5225 @@
 </verb></tscreen>
 
 At this point, you now have debug-enabled software ready.  Let's assume that
-the problem you're having is in the <tt>setup</tt> program.
+the problem you're having is in the <tt>mythtv-setup</tt> program.
 <tscreen><verb>
-$ cd setup
-$ gdb ./mythtv-setup
+$ gdb mythtv-setup
 
 GNU gdb 5.3-1mdk (Mandrake Linux)
 Copyright 2002 Free Software Foundation, Inc.
@@ -5238 +5237 @@
 Type "show copying" to see the conditions.
 There is absolutely no warranty for GDB.  Type "show warranty" for details.
 This GDB was configured as "i586-mandrake-linux-gnu"...
+(gdb) 
+</tscreen><verb>
+At this point, you are at a GDB prompt which is waiting for input. <bf>gdb</bf>
+has many commands that are available for debugging which are not covered here.
+For more in-depth information, read the <tt>man</tt> page.
+
+At the prompt type
+<tscreen><verb>
+(gdb) handle SIG33 nostop
+Signal        Stop      Print   Pass to program Description
+SIG33         No        Yes     Yes             Real-time event 33
 (gdb) handle SIGPIPE nostop
 Signal        Stop      Print   Pass to program Description
 SIGPIPE       No        Yes     Yes             Broken pipe
@@ -5246 +5256 @@
 (gdb)
 </verb></tscreen>
 
-<bf>gdb</bf> has a number of options, read the <tt>man</tt> page for more
-information.
+This sets up the debugging environment so that real-time signals do not stop the 
+debugging session. 
 
-Once at the <tt>(gdb)</tt> prompt, type <tt>run</tt> to start program
-execution.  When the program segfaults or appears to lock-up (press CTRL-C),
-type 
+This is only strictly necessary with Mythfrontend real-time 
+priority option enabled, however it has no effect and does no harm with other 
+debugging. Broken pipes are also not processed, since some Myth components 
+require this signal to complete their error handling, rather than terminating
+the program.
+
+Logging is also enabled, to gdb.txt in the current directory.
+
+Now, type <tt>run</tt> to start program execution.  When the program segfaults
+or appears to lock-up (press CTRL-C), type 
 <tscreen><verb>
 (gdb) thread apply all bt full
 (gdb) set logging off
 </verb></tscreen>
 
-If gdb returns to the gdb prompt with a "Program received signal SIG33,
-Real-time event 33", type <tt>cont</tt> to continue; this is not a "real"
-bug.
-
 All of the output from <tt>gdb.txt</tt> should be posted to the mythtv-dev
 mailing list, along with the steps you followed to get the program to crash.