[mythtv-users] Vaapi use on Sandy Bridge
williammotten at gmail.com
Thu Feb 2 15:37:32 UTC 2012
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.
>>> "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.
>>> mythtv-users mailing list
>>> mythtv-users at mythtv.org
>> 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
>> Sample video of what normally happens
> The latest debug using the latest master.
> Terminal capture
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.
Also I need some feedback whether or not this is helpful or I need to
change or just stop.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the mythtv-users