Ubuntu
mythtv package

mythfrontend.real crashed with SIGSEGV in stdin()

Bug #197880 reported by Alvin Cura on 2008-03-03

Affects		Status	Importance	Assigned to	Milestone
	MythTV	Invalid	Unknown	mythtv-bugs #4946
	mythtv (Ubuntu)	Invalid	Medium	Unassigned

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
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_US.UTF-8
SHELL=/bin/bash
Signal: 11
SourcePackage: mythtv
StacktraceTop:
?? () from /usr/lib/libmythtv-0.21.so.0
?? ()
?? ()
stdin () from /lib/tls/i686/cmov/libc.so.6
?? () from /usr/lib/libmythtv-0.21.so.0
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
SegvAnalysis:
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

See original description

Tags:

Revision history for this message

Alvin Cura (alvinc) wrote on 2008-03-03:

Dependencies.txt Edit (5.0 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (487 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (33.7 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (693 bytes, text/plain; charset="utf-8")
Registers.txt Edit (467 bytes, text/plain; charset="utf-8")
Stacktrace.txt Edit (662 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (8.1 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2008-03-03: Symbolic stack trace

Stacktrace.txt (retraced) Edit (3.0 KiB, text/plain)

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

Revision history for this message

Apport retracing service (apport) wrote on 2008-03-03: Symbolic threaded stack trace

ThreadStacktrace.txt (retraced) Edit (44.7 KiB, text/plain)

Changed in mythtv:
importance:	Undecided → Medium

David Morris (dave-greenacre) on 2008-03-13

Changed in mythtv:
status:	New → Confirmed

Bug Watch Updater (bug-watch-updater) on 2008-09-16

Changed in mythtv:
status:	Unknown → New

Bug Watch Updater (bug-watch-updater) on 2008-09-25

Changed in mythtv:
status:	New → Confirmed

Revision history for this message

Eamonn Sullivan (eamonn-sullivan) wrote on 2009-04-13:

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

Bug Watch Updater (bug-watch-updater) on 2009-07-18

Changed in mythtv:
status:	Confirmed → Unknown

Revision history for this message

Mario Limonciello (superm1) wrote on 2009-08-16:

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 http://mythbuntu.org/auto-builds to enable them.

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

Thanks!

Changed in mythtv (Ubuntu):
status:	Confirmed → Incomplete

Bug Watch Updater (bug-watch-updater) on 2009-08-23

Changed in mythtv:
status:	Unknown → Invalid

Kees Cook (kees) on 2009-09-16

description:

updated

Revision history for this message

Jonathan Thomas (echidnaman) wrote on 2009-09-17:

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!