Good morning everyone. I recently purchased a Synology DS214play running DSM 5. Amazing device! I installed the latest version of PyTivo and the software itself is working well. The problem I have is with my installed version of Tivodecode. I have configured, make, and make install on 0.2pre4. I noticed when clicking the checkbox to decode in pyTivo, that it starts to initialize and then just stops. I then tried to run tivodecode from the command line and any time I try to enter a command I get:
Segmentation Fault (core dumped)
I assume this is what is happening in the background when pytivo calls tivodecode. I found a patched 0.4.4 and installed and I have the same issue. Not sure if maybe it somehow isn't compatible with Synology, etc. Anyone else try this or have any advice? Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
yes, I turned on SSH and was running configure, make, and make install on the Synology. This was after installing Optware, etc for compiling programs. My thought was maybe something isn't quite compatible, but I'm just not sure. I am successfully running pyTivo, it just fails when calling Tivodecode. I found the segmentation fault when I tried executing Tivodecode manually.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm not familiar with the platform at all, but if there is a debugger (like gdb) available could you run it under the debugger and find out where in the code the segmentation fault occurs?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm seeing what looks like the same segmentation fault when I try to compile tivodecode on Synology DS5. I'm using different model, the DS1515+.
I also tried 0.2pre4, then the 0.4.4 patch with the same segmention fault.
I followed the usual advice to compile a third-party tool on a Synology and ran the ipkg bootstrap, then installed optware-devel. It seems like the toolchain that installed is linking against the wrong libc.
When I step through main() on the 0.4.4 patch, it seems that the segfault occurs on the first memset:
168 char * outfile = NULL;
(gdb) s
171 memset(mak, 0, sizeof(mak));
(gdb) s
Program received signal SIGSEGV, Segmentation fault.
0x0805c587 in TuringGen (internal=0x805f578, buf=0x0) at TuringFast.c:298
298 ROUND(12,buf+320);
Good morning everyone. I recently purchased a Synology DS214play running DSM 5. Amazing device! I installed the latest version of PyTivo and the software itself is working well. The problem I have is with my installed version of Tivodecode. I have configured, make, and make install on 0.2pre4. I noticed when clicking the checkbox to decode in pyTivo, that it starts to initialize and then just stops. I then tried to run tivodecode from the command line and any time I try to enter a command I get:
Segmentation Fault (core dumped)
I assume this is what is happening in the background when pytivo calls tivodecode. I found a patched 0.4.4 and installed and I have the same issue. Not sure if maybe it somehow isn't compatible with Synology, etc. Anyone else try this or have any advice? Thanks!
Where are you running "make" for tivodecode - on the DS214?
yes, I turned on SSH and was running configure, make, and make install on the Synology. This was after installing Optware, etc for compiling programs. My thought was maybe something isn't quite compatible, but I'm just not sure. I am successfully running pyTivo, it just fails when calling Tivodecode. I found the segmentation fault when I tried executing Tivodecode manually.
I'm not familiar with the platform at all, but if there is a debugger (like gdb) available could you run it under the debugger and find out where in the code the segmentation fault occurs?
I will try to figure this out over the holiday and post my results. Thanks!
Last edit: David Henry 2014-11-26
I'm seeing what looks like the same segmentation fault when I try to compile tivodecode on Synology DS5. I'm using different model, the DS1515+.
I also tried 0.2pre4, then the 0.4.4 patch with the same segmention fault.
I followed the usual advice to compile a third-party tool on a Synology and ran the ipkg bootstrap, then installed optware-devel. It seems like the toolchain that installed is linking against the wrong libc.
When I step through
main()on the 0.4.4 patch, it seems that the segfault occurs on the first memset:The same segmentation fault happened on a simple example of using memset.
Eventually, I got tivodecode compiled using a Debian chroot instead.