[mythtv-users] mythtv-common-0.26.0-1.fc17.x86_64 giving errors in abrt daemon on startup

[Bill Meek]

On 12/02/2012 08:13 PM, Jerry wrote:
> Here is output from a crash that happened this afternoon.  I'm not sure if
> this backtrace is equivalent to what you are referring to.
...
> [root at sirius ccpp-2012-12-02-14:43:07-2122]# more core_backtrace
> cc10c72da62c93033e227ffbe2670f2c4fbbde1a 0x35935 raise /lib64/libc.so.6
> f33186a4c862fb0751bca60701f553b829210477
> cc10c72da62c93033e227ffbe2670f2c4fbbde1a 0x370e8 abort /lib64/libc.so.6
> 352bc5cf09233cea84fd089527a146cfb5b7d8dc
> cc10c72da62c93033e227ffbe2670f2c4fbbde1a 0x2e6a2 __assert_fail_base
> /lib64/libc.so.6 985cad4c0d01e51136a4033696476fe616cc6d7d
> cc10c72da62c93033e227ffbe2670f2c4fbbde1a 0x2e752 __assert_fail
> /lib64/libc.so.6 -
> 704aa861b9d32507ded81dd8cdf8577d053361fc 0x8e30 - /lib64/libmythnzmqt.so.0
> 844cdba0f601ea41c6b91ffa7fbd83da2da4257b
> 704aa861b9d32507ded81dd8cdf8577d053361fc 0xc7f8 - /lib64/libmythnzmqt.so.0
> bef51a4b3c03e7adf1009d4febf2ac2fab772f19
> 8521a74f5b8164a36e245af9524fb7d0be9e1203 0x10f8a1 -
> /lib64/libmythbase-0.26.so.0 c6570a41179bc462a0e882ead70c08ce0ef209c2
> d1e01c71534f1e41fe10f0aed58b3bf6711aadfb 0x7b7bc - /lib64/libQtCore.so.4
> 52c6044b46de75bcba060fa79f7482d349610223
>   0xaa764 - /usr/lib64/nvidia/libGL.so.1
> 69bdd1dd02093527d72da8890aca3cbd5a6d7006
> 699e7556b23d23a857371af778a5394a7149da61 0x7d14 start_thread
> /lib64/libpthread.so.0 b0385609f3dd5ea1b79d56946826dcbb1b62d86f
> cc10c72da62c93033e227ffbe2670f2c4fbbde1a 0xf168d clone /lib64/libc.so.6
> e256aa64ea4f21c9e32cd0f782dbc840f150a5b3
> [root at sirius ccpp-2012-12-02-14:43:07-2122]# more reason
> Process /usr/bin/mythlogserver was killed by signal 6 (SIGABRT)
> [root at sirius ccpp-2012-12-02-14:43:07-2122]#
>
> Does that help to clarify what is going on?  This time, it seems to be a
> different signal (failed assertion?).

Hi;

Sorry, no. Here's a link to a proper backtrace, just so you can see what
it looks like:

     http://code.mythtv.org/trac/attachment/ticket/11043/gdb-mythlogserver-5058.txt

It's the output of running gdb on a core file, not an ASCII text file.

An ls -l of a core file on my ubuntu box look similar to this 206MB file:

     -rw------- 1 bill bill 206643200 Aug  2 16:43 /tmp/core.1343943786.1000.5017.mythlogserver

But the format is distribution/option dependent.

In my experience on this list and with Trac, the output above will not
provide enough information for problem resolution.

Any Fedora users watching that can tell Jerry where his core files are?

-- 
Bill