[mythtv] [Q]: anybody with sporadic segfault with latest trunk?

[Robert McNamara]

On Tue, Dec 22, 2009 at 9:57 AM, myShade <myshade at bredband.net> wrote:
> On Tue, 2009-12-22 at 13:47 -0400, Emmanuel wrote:
>> Hi all,
>> sorry to be so unspecific but I got several mythbackend segfaults (I
>> only realized that later) with latest trunk. Since then I am running the
>> backend under gdb but, obviously, nothing has happened yet. So I figured
>> I would ask to see if there was some specific part I would have to
>> exercise to make it happen ;-)
>> I use Karmic up to date:
>> Here is the log in dmesg: the first one is by far the most frequent
>>
>> mythbackend[8151]: segfault at 10 ip 02e9a264 sp b670c17c error 4 in
>> libmyth-0.22.so.0.22.0[2df0000+44d000]
>>
>> [53201.571161] mythbackend[1659]: segfault at 84 ip 07923a67 sp b6f980c0
>> error 4 in libQtCore.so.4.5.2[78da000+22b000]
>>
>> the following ones happen with transcode (the transcoded files seem to
>> be ok):
>> [106871.652572] mythtranscode[22945]: segfault at db302444 ip 073fda69
>> sp b68a8000 error 5 in libQtCore.so.4.5.2[73b4000+22b000]
>>
>> [107228.866544] mythtranscode[23058]: segfault at 6 ip 009bda00 sp
>> b69b80c0 error 4 in libmythdb-0.22.so.0.22.0[972000+99000]
>
> Hi.
> Yes, Yesterday. Not yet today...( updated to rev 22997 ).
>
> Fredrik
>

It is impossible to say that any two segfaults are the same without
the both of you having a backtrace.  None of the above allows one to
conclude anything helpful, unfortunately.  You'll need to get a
backtrace.

Robert