mythfrontend.real crashed with SIGSEGV in stdin()

Bug #197880 reported by Alvin Cura on 2008-03-03
Affects Status Importance Assigned to Milestone
mythtv (Ubuntu)

Bug Description

Binary package hint: mythtv

Running hardy, latest packages as of March 1

ProblemType: Crash
Architecture: i386
Date: Sun Mar 2 20:32:39 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/mythfrontend.real
NonfreeKernelModules: nvidia
Package: mythtv-frontend 0.21.0~fixes16259-0ubuntu1
PackageArchitecture: i386
ProcCmdline: /usr/bin/mythfrontend.real --logfile /tmp/mythfrontend.6737.log
Signal: 11
SourcePackage: mythtv
 ?? () from /usr/lib/
 ?? ()
 ?? ()
 stdin () from /lib/tls/i686/cmov/
 ?? () from /usr/lib/
Title: mythfrontend.real crashed with SIGSEGV in stdin()
Uname: Linux 2.6.24-10-generic i686
UserGroups: adm admin audio cdrom dialout floppy lpadmin mythtv netdev plugdev powerdev sambashare scanner video
 Segfault happened at: 0xb7dff9fc: movzwl (%eax),%edi
 PC (0xb7dff9fc) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA

Alvin Cura (alvinc) wrote :

StacktraceTop:process_command (vm=0x921bff0, link_values=
vm_start (vm=0x921bff0) at vm.c:290
dvdnav_part_play (this=0x82fe350, title=0, part=1) at navigation.c:158
dvdnav_title_play (this=0x0, title=0) at navigation.c:139
DVDRingBufferPriv::OpenFile (this=0x95b2398, filename=@0xac19c690) at DVDRingBuffer.cpp:167

Changed in mythtv:
importance: Undecided → Medium
Changed in mythtv:
status: New → Confirmed
Changed in mythtv:
status: Unknown → New
Changed in mythtv:
status: New → Confirmed

I tried to get more info on the segfault using valgrind and found that the program *doesn't* crash when run this way. Might be a clue:

G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log /usr/bin/mythfrontend.real

Changed in mythtv:
status: Confirmed → Unknown
Mario Limonciello (superm1) wrote :

Hi, thanks for the bug report. Upstream has stopped focusing on 0.21 based reports in preparation for a 0.22 release later this year. Can you please try to see if this bug is reproducible on 0.22? If it is, we can try to forward this information to the bug upstream to get the right eyes focused on it.

We have builds of mythtv 0.22 available on a PPA to test. Please follow the directions at to enable them.

WARNING: If you intend to go back to 0.21, you will need to back up your database before upgrading.


Changed in mythtv (Ubuntu):
status: Confirmed → Incomplete
Changed in mythtv:
status: Unknown → Invalid
Kees Cook (kees) on 2009-09-16
description: updated
Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in mythtv (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.