[mythtv] Ticket #10483: mythtranscode crasshes when using --profile for lossless transcodes

Kenni Lund kenni at kelu.dk
Thu Mar 22 21:43:53 UTC 2012

2012/3/22 Steven Adeff <adeffs.mythtv at gmail.com>:
> On Thu, Mar 22, 2012 at 3:08 PM, Kenni Lund <kenni at kelu.dk> wrote:
>> 2012/3/22 Steven Adeff <adeffs.mythtv at gmail.com>:
>>> On Thu, Mar 22, 2012 at 1:34 PM, Michael T. Dean
>>> <mtdean at thirdcontact.com> wrote:
>>>> On 03/22/2012 01:30 PM, Steven Adeff wrote:
>>>>> On Thu, Mar 22, 2012 at 1:24 PM, Michael T. Dean wrote:
>>>>>> On 03/22/2012 01:14 PM, Steven Adeff wrote:
>>>>>>> On Thu, Mar 22, 2012 at 12:18 PM, Michael T. Dean wrote:
>>>>>>>> On 03/22/2012 10:56 AM, Steven Adeff wrote:
>>>>>>>>> On Wed, Mar 21, 2012 at 2:30 PM,<noreply at mythtv.org>      wrote:
>>>>>>>>>> #10483: mythtranscode crasshes when using --profile for lossless transcodes
>>>>>>>>>> -------------------------------------+-----------------------------
>>>>>>>>>>     Reporter:  adeffs.mythtv@…          |          Owner:  beirdo
>>>>>>>>>>        Type:  Bug Report - General     |         Status:  assigned
>>>>>>>>>>     Priority:  minor                    |      Milestone:  unknown
>>>>>>>>>> Component:  MythTV - Mythtranscode   |        Version:  Master Head
>>>>>>>>>>     Severity:  medium                   |     Resolution:
>>>>>>>>>>     Keywords:  transcode                |  Ticket locked:  0
>>>>>>>>>> -------------------------------------+-----------------------------
>>>>>>>>>> Changes (by beirdo):
>>>>>>>>>>     * owner:   =>      beirdo
>>>>>>>>>>     * status:  new =>      assigned
>>>>>>>>>> --
>>>>>>>>>> Ticket URL:<http://code.mythtv.org/trac/ticket/10483#comment:3>
>>>>>>>>>> MythTV<http://code.mythtv.org/trac>
>>>>>>>>>> MythTV Media Center
>>>>>>>>> Gavin,
>>>>>>>>> I'm trying to get this apport report uploaded to launchpad, but am
>>>>>>>>> having issues.  Michael was helping me on the users list with the
>>>>>>>>> issue initially. Let me know if you can use this crash report or if
>>>>>>>>> there is another way I can get the info to you when using the
>>>>>>>>> mythbuntu autobuilds. Otherwise I'll compile from source to get the
>>>>>>>>> standard segfault report data.
>>>>>>>> You should be able to do a "normal" run of gdb directly using the
>>>>>>>> packaged version (and as long as you install the debug symbols package,
>>>>>>>> it should have all information we need).  The apport stuff is just
>>>>>>>> supposed to make things easier/automatic, but you don't have to use it.
>>>>>>>> http://www.mythtv.org/wiki/Debugging#Getting_a_Backtrace
>>>>>>>> Mike
>>>>>>> I finally got it to go!
>>>>>>> https://bugs.launchpad.net/mythbuntu/+bug/962353
>>>>>>> Let me know if that doesn't provide what you need and I'll do an "old
>>>>>>> school" gdb version.
>>>>>> I think you need to make it public so we can see it.  (Probably some
>>>>>> link to click on the page itself?)
>>>>> try now
>>>> Works, and the back trace looks good.
>>>> Thanks,
>>>> Mike
>>> great! I'm going to update the wiki for the process.
>> If you're talking about the process of changing the launchpad bug
>> report from private to public, then please don't....that action is
>> reserved for *buntu developers. The launchpad bug reports are
>> intentionally kept private until a developer has extracted the
>> relevant parts from the core dump and deleted the actual dump. You can
>> read the reasoning for keeping it private here (halfway down in the
>> linked section):
>> https://wiki.ubuntu.com/Apport#How_to_enable_apport
> Then we should remove apport from the mythtv wiki, at least until the
> mythtv dev's have a way of extracting the information from the crash
> report file without having to rely on launchpad.

No, but perhaps some of the text should be rephrased. Apport is a
reasonable option for those users who already has it set up, who don't
want to spend time manually creating (MythTV) Trac tickets or who
don't want to run gdb directly for whatever reason. An automatic bug
report filed to Ubuntu launchpad (with the possibility of it getting
upstreamed to MythTV Trac at some point) is still better than no
report to either Ubuntu or MythTV. If you submit a ticket to MythTV
Trac, the logging data and the backtrace should be sent to the MythTV
Trac ticket - not to some other bug report over at the Ubuntu
launchpad site.

As Michael said, you don't have to compile from source to get the
backtrace with the Ubuntu packages, you just need to install the debug
packages and run the relevant MythTV executable under gdb. If you have
the core dump from Apport, you can even run gdb against it (also
described on the wiki page) and extract the backtrace yourself for the
MythTV ticket.

Best regards

More information about the mythtv-dev mailing list