[mythtv-users] Failed with exit status 140
Michael T. Dean
mtdean at thirdcontact.com
Mon Jun 10 15:03:23 UTC 2013
On 06/10/2013 09:38 AM, Michael T. Dean wrote:
> That said, your specific abort is occurring when MythTV starts a
> MythTimer (
> https://github.com/MythTV/mythtv/blob/bfd24081b347ced053b7eeb1bbda1ddea572a56a/mythtv/libs/libmythbase/mythtimer.h#L12
> ), which calls QTime::start(), which calls QTime::currentTime() (both
> from Qt), which calls __tzset(), which calls tzset_internal() (both
> from glibc/eglibc), which (it seems--though not knowing exactly which
> version of eglibc you're using, I'm just guessing) is trying to free a
> pointer for the old_tz (which stores the value for the previously-set
> time zone) by calling free() (from glibc/eglibc), but that pointer
> seems to be pointing to an invalid area of memory.
>
> So, while I can't, at this point, say the problem is with
> eglibc/glibc, I can say it could well be a problem with eglibc/glibc,
> with Qt, or MythTV's use of one of those libraries. And, since the
> MythTV code that calls the functions that eventually abort is just
> calling start() on (what seems to be a valid) QTime, it seems like
> there's a good chance the issue is lower level than MythTV. And, if
> the issue isn't reproducible on lots of similar systems (i.e. using
> the same (e)glibc/Qt/MythTV versions), it could well be even lower
> level (such as memory issues or ...).
>
> I'll see if anyone else can see a problem in MythTV's code, but at
> this point, I think the problem is actually in one of the libraries.
> Unfortunately, I don't see any other reports of similar issues out there.
>
> If you can easily reproduce the issue, it would be interesting to see
> the value of old_tz at the point of the failure. You'd have to get
> this information by using gdb interactively. To do this, just make
> sure you have the MythTV debug package installed, then start up gdb
> directly as described at
> http://www.mythtv.org/wiki/Debugging#Getting_a_Backtrace , and see the
> gdb manual for more (
> http://sourceware.org/gdb/current/onlinedocs/gdb/ ).
Oh, and Daniel K. just pointed out that unstable/development is no
longer using a QTime for MythTimer, so it's likely that this issue won't
occur in development, or in 0.27 (when released).
Mike
More information about the mythtv-users
mailing list