[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Crash with XBMC from backports



Hi Julius,

2014-03-26 20:46 GMT+01:00 Julius Schwartzenberg
<julius.schwartzenberg@gmail.com>:
> Bálint Réczey wrote:
>> Based on the stack trace it looks like to be something different:
>>
>> #0 0x00000000 in ?? ()
>> #1 0x08642116 in CGUIFontTTFGL::Begin() ()
>> #2 0x085bdef6 in CGUIFont::Begin() ()
>> #3 0x08611846 in CGUITextLayout::Render(float, float, float, unsigned
>> int, unsigned int, unsigned int, float, bool) ()
>> #4 0x085d7399 in CGUILabel::Render() ()
>> #5 0x0859a32e in CGUIButtonControl::RenderText() ()
>> #6 0x0859a391 in CGUIButtonControl::Render() ()
>> #7 0x085a18cd in CGUIControl::DoRender() ()
>> ...
>>
>> On i386 XBMC is compiled for i486, see
>> https://buildd.debian.org/status/fetch.php?pkg=xbmc&arch=i386&ver=2%3A12.3%2Bdfsg1-3~bpo70%2B2&stamp=1390146700
>>
>> If you could recompile the package without stripping and could provide
>> a more detailed stack-trace we could debug this further.
>
> Thanks for your response. I just created a new log file with unstripped
> XBMC packages:
> http://yadi.sk/d/Rjd6OXp6LGmvR
The log still does not contain more info, loading the coredump to gdb
and creating 'bt full' would have given more clue.
Based on the previous log you have probably hit this problem with old
video cards:
http://forum.xbmc.org/showthread.php?tid=151330&pid=1456454#pid1456454

Please test the workarounds and if they don't help please provide a
full back-trace using gdb.

Cheers,
Balint


Reply to: