mythbuntu-bugs team mailing list archive

[Bug Watch Updater <490920@xxxxxxxxxxxxxxxxxx>]

** Changed in: mythtv
       Status: New => Confirmed

-- 
mythfilldatabase crashes
https://bugs.launchpad.net/bugs/490920
You received this bug notification because you are a member of Mythbuntu
Bug Team, which is subscribed to mythtv in ubuntu.

Status in MythTV: Confirmed
Status in “mythtv” package in Ubuntu: Triaged

Bug description:
Binary package hint: mythtv

Crashed when running guide updates.

ProblemType: Crash
Architecture: i386
CrashDB: mythbuntu
Date: Tue Dec  1 01:13:19 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/mythfilldatabase
NonfreeKernelModules: nvidia
Package: mythtv-backend 0.22.0+fixes22936-0ubuntu0+mythbuntu3
ProcCmdline: /usr/bin/mythfilldatabase
ProcCwd: /
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/sh
ProcVersionSignature: Ubuntu 2.6.31-15.50-generic
SegvAnalysis:
 Segfault happened at: 0x503f3c <_ZN6MythDB18ClearSettingsCacheE7QStringS0_+28>:	mov    (%edi),%eax
 PC (0x00503f3c) ok
 source "(%edi)" (0x0f19b60f) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: mythtv
StacktraceTop:
 MythDB::ClearSettingsCache (this=0xf19b60f, myKey=..., newVal=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
 MythContext::ClearSettingsCache (this=0x95cd708, myKey=DWARF-2 expression error: DW_OP_reg operations must be used either alone or in conjuction with DW_OP_piece.
 MythContext::readyRead (this=0x95cd708, sock=0x95c4a68) at mythcontext.cpp:2171
 MythSocketThread::ReadyToBeRead (this=0x9579d58, sock=0x95c4a68) at mythsocketthread.cpp:168
 MythSocketThread::run (this=0x9579d58) at mythsocketthread.cpp:355
Title: mythfilldatabase crashed with SIGSEGV in MythDB::ClearSettingsCache()
Uname: Linux 2.6.31-15-generic i686
UserGroups: audio cdrom dialout video
XsessionErrors: (polkit-gnome-authentication-agent-1:2116): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed