Opened 14 years ago

Closed 14 years ago

Last modified 14 years ago

#9987 closed Bug Report - General (Invalid)

Mythfrontend segfault on LiveTV channel change

Reported by: Peter Townsend <elpinkus@…> Owned by:
Priority: minor Milestone: unknown
Component: MythTV - General Version: Master Head
Severity: medium Keywords:
Cc: Ticket locked: no

Description

I have a frontend that usually crashes when I change channels in Live TV.

Run mythfrontend, select Watch TV. Live TV starts normally. Change channels either by pressing down and then select or through the program guide and mythfrontend crashes.

Attachments (5)

mythfrontend.log​ (81.3 KB ) - added by Peter Townsend <elpinkus@…> 14 years ago.
Frontend log
mythbackend.log​ (20.5 KB ) - added by Peter Townsend <elpinkus@…> 14 years ago.
Backend log
mythfrontendgdb.txt​ (53.4 KB ) - added by Peter Townsend <elpinkus@…> 14 years ago.
Frontend backtrace
versions.txt​ (1.6 KB ) - added by Peter Townsend <elpinkus@…> 14 years ago.
--version output (v0.25pre-3052-gf659892)
mythtv_backtrace.txt​ (62.0 KB ) - added by elpinkus@… 14 years ago.
Backtrace attempt #2

Download all attachments as: .zip

Change History (10)

by Peter Townsend <elpinkus@…>, 14 years ago

Attachment: mythfrontend.log​ added

Frontend log

by Peter Townsend <elpinkus@…>, 14 years ago

Attachment: mythbackend.log​ added

Backend log

by Peter Townsend <elpinkus@…>, 14 years ago

Attachment: mythfrontendgdb.txt​ added

Frontend backtrace

by Peter Townsend <elpinkus@…>, 14 years ago

Attachment: versions.txt​ added

--version output (v0.25pre-3052-gf659892)

comment:1 by danielk, 14 years ago

Status: new → infoneeded_new

Peter, we need a backtrace from a segfault or similar. It looks like you forgot to clear a breakpoint in the attached backtrace.

comment:2 by Peter Townsend <elpinkus@…>, 14 years ago

I don't actually know how to use GDB, I just copied commands off the debugging wiki page so I don't know how I got it wrong.

Naturally, after crashing regularly for weeks, the moment I created this ticket my system started behaving itself perfectly and I haven't had another crash since.

I'll open another ticket if I see it again =/

comment:3 by danielk, 14 years ago

Resolution: → Invalid
Status: infoneeded_new → closed

Peter, I'm going to close this as invalid for insufficient info for now.

The best way to capture a segfault for analysis later is to get a coredump. You do this by running "ulimit -c unlimited" before you run the program you want info on. Then when it eventually crashes you run "gdb which name_of_program core" and type in the commands to get the information, in this case "thread apply all bt" hit return until it finishes scrolling and then cut and paste everything from the when you started gdb to a file. Then keep the core file. If some piece of debugging info is missing it can sometimes be added after the fact if you have still have the core dump.

by elpinkus@…, 14 years ago

Attachment: mythtv_backtrace.txt​ added

Backtrace attempt #2

comment:5 by Peter Townsend <elpinkus@…>, 14 years ago

The day after I gave up, the crashes started again.

I'm attaching what I hope is a useful backtrace.

I'm now running v0.25pre-3155-g1067f8c.

Note: See TracTickets for help on using tickets.