[mythtv] [mythtv-commits] Ticket #1278: mythfrontend crashes on leaving program guide

Simon Kenyon simon at koala.ie
Fri Feb 17 12:35:44 UTC 2006

Isaac Richards wrote:

>On Friday 17 February 2006 03:32, Simon Kenyon wrote:
>>On Friday 17 February 2006 01:37, MythTV wrote:
>>>#1278: mythfrontend crashes on leaving program guide
>>>-- - Reporter:  anonymous  |        Owner:  ijr
>>>     Type:  defect     |       Status:  closed
>>> Priority:  minor      |    Milestone:
>>>Component:  mythtv     |      Version:  head
>>> Severity:  medium     |   Resolution:  invalid
>>>-- - Changes (by ijr):
>>>  * resolution:  => invalid
>>>  * status:  reopened => closed
>>> Backtraces weren't from myth compiled in debug mode:
>>> http://www.mythtv.org/docs/mythtv-HOWTO-22.html#ss22.2
>>you closed it saying that it wasn't for myth compiled in debug mode
>>i always build in debug mode
>>what have i done wrong?
>Look at the backtrace.  See all the '(no debugging symbols found)' lines at 
>the start?  All the lines like '#3  0x08325018 in ?? ()' later on?  Means 
>that it wasn't compiled in debug mode.  Couldn't tell you what you did wrong.

i accept that
i've been using an ebuild to do the compile/install
i don't know where, but this must be doing something strange
as the build progresses i see the message that it is compiling in debug 
mode (oh well)

after a bit of digging, it appears that gentoo ebuilds by default strip 
this might explain some of the bogus backtraces that you have been getting.

anyway, to avoid any ambiguity, i'm going back to the old way of doing 
it by hand.
just written a shell script which does the whole process of 
have tested on my fastest machine.
will now run it on all the others and run frontend and two backends 
under gdb to try and
catch a valid trace. should have that for you later today.


More information about the mythtv-dev mailing list