[ATrpms-users] MythTV 178 Crashes on Recording Start

[Kirk Bocek]

Axel Thimm wrote:
> Usually it is enough to have the debuginfo installed to get sensible
> output from gdb. When the debuginfo packages first came to life there
> wasn't much docu, maybe this has changed by now, but I wouldn't have
> any links to such documentation. For me it always worked to just
> install the debuginfo package and then gdb would be enriched with
> proper symbols.

Here's my output when I fire off gdb:

$gdb mythbackend -x gdbcommands
GNU gdb Red Hat Linux (6.3.0.0-1.153.el4_6.2rh)
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu"...(no debugging symbols 
found)
Using host libthread_db library "/lib64/tls/libthread_db.so.1".

(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47103275530400 (LWP 15205)]
...


After that there is a dozen or so 'New Thread' lines. Mythbackend seems to be 
running fine after that. Is the 'debugging symbols' message a problem?

Kirk Bocek