[mythtv-users] Vaapi use on Sandy Bridge

[william otten]

On Sat, Jan 28, 2012 at 10:16 PM, william otten <williammotten at gmail.com>wrote:

>
>
> On Sat, Jan 28, 2012 at 3:37 PM, william otten <williammotten at gmail.com>wrote:
>
>>
>>
>> On Sat, Jan 28, 2012 at 3:05 PM, Michael T. Dean <mtdean at thirdcontact.com
>> > wrote:
>>
>>> On 01/28/2012 02:06 PM, william otten wrote:
>>> > Cocerning debugging, I have attached the gdb and myth files. I ran the
>>> > repeatable test several times. Let me know if further info is needed.
>>>
>>> The gdb log seems to be missing any backtrace.  You actually need to
>>> stop the program somehow to get a backtrace--that means either crash it,
>>> or interrupt it (with Ctrl-C) when it's locked up or doing whatever is
>>> wrong, or set a breakpoint in gdb if you know exactly where you want it
>>> to stop.
>>>
>>> http://www.mythtv.org/wiki/Debugging#Executing_the_application_under_gdb
>>> "When the application crashes or is terminated, gdb will automatically
>>> output a backtrace to the file |gdb.txt| in the current working
>>> directory. If the MythTV program appears to be locked up and does not
>>> crash, press CTRL-C to create the backtrace file."
>>>
>>> (Ctrl-C also applies when it's not locked, but is doing whatever it
>>> shouldn't be doing)
>>>
>>> As far as posting the logs, you can either a) post to a site that
>>> doesn't have the file size limits that mailing lists have (such as
>>> dropbox or google docs or some pastebin or something) and then provide a
>>> link in your e-mail or b) compress the files before sending the e-mail.
>>> Ideally, you'll post somewhere else (rather than compressing and sending
>>> as an attachment) where people can access the content without having to
>>> download a file, save it, uncompress it, then open it to look.
>>>
>>> Mike
>>> _______________________________________________
>>> mythtv-users mailing list
>>> mythtv-users at mythtv.org
>>> http://www.mythtv.org/mailman/listinfo/mythtv-users
>>>
>> The first attempts I did try to use control c but being new to this
>> method took some trial and error. I was able to capture what was in
>> terminal this time where as the previous attempts didn't allow that.
>> Here are the links:
>> Terminal capture
>>
>> http://dl.dropbox.com/u/17574275/Myth%20backtrace
>>
>> gdb.txt
>>
>> http://dl.dropbox.com/u/17574275/gdb.txt
>>
>> myth.log
>>
>> http://dl.dropbox.com/u/17574275/myth.log
>>
>> Sample video of what normally happens
>>
>> http://dl.dropbox.com/u/17574275/Mythtv%2025%20issue.webm
>>
> The latest debug using the latest master.
> Terminal capture
>
> http://dl.dropbox.com/u/17574275/Myth%20Backtrace%201-28-12
>
> gdb.txt
>
> http://dl.dropbox.com/u/17574275/gdb%201-28-12.txt
>
> myth.log
>
> http://dl.dropbox.com/u/17574275/myth%201-28-12.log
>
The latest debug using the latest master and I got an update from
xorg-edgers. I don't know if it included the patch for the opengl issue or
not. I tried running the debug three times: 1st attempt I let the debug run
its course and the 2nd and 3rd times I tried to end it by using control-c.
Terminal capture

http://dl.dropbox.com/u/17574275/MythBacktrace%202-2-12

gdb.txt

http://dl.dropbox.com/u/17574275/gdb%202-2-12.txt

myth.log

http://dl.dropbox.com/u/17574275/myth%202-2-12.log

Also I need some feedback whether or not this is helpful or I need to
change or just stop.
Thanks
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.mythtv.org/pipermail/mythtv-users/attachments/20120202/7cb5d023/attachment.html