Project

General

Profile

Actions

Bug #70

closed

Segfault attempt to run

Added by Anonymous over 15 years ago. Updated over 15 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Start date:
01/25/2009
Due date:
% Done:

100%

Estimated time:

Description

Jan 25 10:33:01 upstairs kernel: vdr12753: segfault at 80 ip b6b735ff sp bf86ff40 error 6 in libvdr-yaepghd.so.1.6.0[b6b30000+54000]

What other information do you need to work on this?

Actions #1

Updated by bball over 15 years ago

  • Status changed from New to Assigned
  • Assignee set to bball

Sorry, the code is currently a work in progress (no official release yet). I will try to get the plugin to work with a fresh vdr install to see whats going on.

Actions #2

Updated by CR7 over 15 years ago

bball wrote:

Sorry, the code is currently a work in progress (no official release yet). I will try to get the plugin to work with a fresh vdr install to see whats going on.

---
Hello,

the bt brings me to this: yaeghd:944
-->
void UpdateTime(time_t newTime) { startTime = newTime; Generate(); }

Might be reason:
yaepghd:927 int startTime <- should be time_t ?

---
Another possible reason: out of bounds access
Line 1992: char freqs4[32]; <-- should be char freqs5[32];
Line 2112: freqs5[0] = '\0'; <-- should be freqs4[0] = '\0';

Actions #3

Updated by bball over 15 years ago

CR7 wrote:

bball wrote:

Sorry, the code is currently a work in progress (no official release yet). I will try to get the plugin to work with a fresh vdr install to see whats going on.

---
Hello,

the bt brings me to this: yaeghd:944
-->
void UpdateTime(time_t newTime) { startTime = newTime; Generate(); }

Might be reason:
yaepghd:927 int startTime <- should be time_t ?

This would not cause a segfualt.

---
Another possible reason: out of bounds access
Line 1992: char freqs4[32]; <-- should be char freqs5[32];
Line 2112: freqs5[0] = '

This code is part of the record dialog box which is a feature that hasn't been implemented yet so I don't think this could be causing it either. That being said this is a bug and I will fix it.

Can you post a complete stack trace ? Also, another thing to check is that the yaepghd plugin directory has the correct contents. The README is a bit unclear about this but the contents of the plugins "themes" directory should be in the "yaepghd" plugin dir. For example on my system I have "/etc/vdr" as my VDR config dir, here are the contents of my yaepghd dir:

# ls -R /etc/vdr/plugins/yaepghd
/etc/vdr/plugins/yaepghd:
default default.theme

/etc/vdr/plugins/yaepghd/default:
bg.png

Actions #4

Updated by CR7 over 15 years ago

Hi bball,

ok - the problem was the theme. Should be checked somewhere :)
So now it works here. Thanks a lot.

I'll have a closer look at, because I like it.
But I'm think the font is by far too large here, so may be I will try me on a theme to let it look like skinreel.

Actions #5

Updated by bball over 15 years ago

  • Status changed from Assigned to Closed
  • % Done changed from 0 to 100

Glad you got it working. In regards to the font, are you sure you registered the theme font with fontconfig? There are instruction in the README on how to do this.

Actions

Also available in: Atom PDF