mythfilldatabase crashed with SIGSEGV in MythContext::ClearSettingsCache() - mythfilldatabase assert failure: *** glibc detected *** /usr/bin/mythfilldatabase: corrupted double-linked list: 0x085b28a0 ***

Bug #428238 reported by BCboy
48
This bug affects 7 people
Affects Status Importance Assigned to Milestone
mythtv (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: mythtv

mythfilldatabase must have been updating in the background.

ProblemType: Crash
Architecture: i386
AssertionMessage: *** glibc detected *** /usr/bin/mythfilldatabase: corrupted double-linked list: 0x085b28a0 ***
CrashCounter: 1
Date: Fri Sep 11 18:48:32 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/mythfilldatabase
NonfreeKernelModules: nvidia
Package: mythtv-backend 0.22.0~trunk21742-0ubuntu2
ProcCmdline: /usr/bin/mythfilldatabase
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-10.32-generic
Signal: 6
SourcePackage: mythtv
StacktraceTop:
 __kernel_vsyscall ()
 raise () from /lib/tls/i686/cmov/libc.so.6
 abort () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? () from /lib/tls/i686/cmov/libc.so.6
Title: mythfilldatabase assert failure: *** glibc detected *** /usr/bin/mythfilldatabase: corrupted double-linked list: 0x085b28a0 ***
Uname: Linux 2.6.31-10-generic i686
UserGroups: audio cdrom dialout video

Revision history for this message
BCboy (hans-urbanerosion) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:__kernel_vsyscall ()
*__GI_raise (sig=6)
*__GI_abort () at abort.c:92
__libc_message (do_abort=2,
malloc_printerr (action=<value optimized out>,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in mythtv (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
visibility: private → public
Revision history for this message
MarcRandolph (mrand) wrote : Re: (SIGSEGV in MythDB::ClearSettingsCache) mythfilldatabase assert failure: *** glibc detected *** /usr/bin/mythfilldatabase: corrupted double-linked list: 0x085b28a0 ***

Howdy, and thank you for helping to improve Mythbuntu by reporting this issue.
This problem has been seen by a few other users, and is still under investigation.

Looks like the assert was likely caused by the same thing as the SIGSEGV in MythDB::ClearSettingsCache reports:

#14 0x003e27c9 in MythDB::ClearSettingsCache ()
   from /usr/lib/libmythdb-0.22.so.0
No symbol table info available.

summary: - mythfilldatabase assert failure: *** glibc detected ***
- /usr/bin/mythfilldatabase: corrupted double-linked list: 0x085b28a0 ***
+ (SIGSEGV in MythDB::ClearSettingsCache) mythfilldatabase assert failure:
+ *** glibc detected *** /usr/bin/mythfilldatabase: corrupted double-
+ linked list: 0x085b28a0 ***
Changed in mythtv (Ubuntu):
status: New → Confirmed
Revision history for this message
MarcRandolph (mrand) wrote :

One suggestion I found via google:

"Chances are very good that it is a pointer problem. valgrind is particularly
good at tracking down pointer problems, so I suggest you take a look at that"

MarcRandolph (mrand)
summary: - (SIGSEGV in MythDB::ClearSettingsCache) mythfilldatabase assert failure:
- *** glibc detected *** /usr/bin/mythfilldatabase: corrupted double-
- linked list: 0x085b28a0 ***
+ mythfilldatabase crashed with SIGSEGV in
+ MythContext::ClearSettingsCache() - mythfilldatabase assert failure: ***
+ glibc detected *** /usr/bin/mythfilldatabase: corrupted double-linked
+ list: 0x085b28a0 ***
Revision history for this message
MarcRandolph (mrand) wrote :

Howdy, and thank you for helping to improve Mythbuntu by opening this ticket. Unfortunately, this backtrace attached is not useful to the developers. Could both of you please open new tickets after following the "basic backtrace" directions outlined here:

http://www.mythtv.org/wiki/Debugging#Debugging_with_Ubuntu_packages

The above process will result in new tickets being opened, so I'm going to close this one. Please ignore the "Invalid" wording - that is simply unfortunate wording.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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