Closed nsajko closed 9 years ago
Coredumps are dependent on the specifics of binary you use (and exact versions of libraries, etc, bla, bla). http://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces does a great explanation of how to get good backtraces. (Obviously you should skip the Gentoo stuff if you're not on Gentoo.) The last listing should be particularly useful.
On Sun Feb 15 2015 at 4:25:34 PM Neven Sajko notifications@github.com wrote:
When I tried to close the application, a segmentation fault happened.
Coredump:
BTW, it couldn't display any imagefiles or videos while running.
— Reply to this email directly or view it on GitHub https://github.com/tomvanbraeckel/3dfsb/issues/10.
OK, I loaded the core dump in gdb and here are backtraces from 3 threads: (gdb) t a a backtrace Thread 3 (Thread 0x7f174d72c8c0 (LWP 8412)):
Thread 2 (Thread 0x7f1736ca9700 (LWP 8444)):
Thread 1 (Thread 0x7f1736290700 (LWP 8451)):
Interesting. Looks like you exited while the texture making thread was still running, doing the getpixel() operation on a surface that comes from GStreamer. That x=30245 shouldn't be... let me dig into the code... thanks a lot for the report!
Hmm, was this with the latest version from GIT of release 1.2 or older? In my 3dfsb.c at line 599, there is no getpixel() function... This logic has been moved to media.c before the 1.2 came out... Can you try again with at least the 1.2 release? Thanks!
When exiting, GStreamer is cleaned up but the texture rendering thread was not explictly stopped (the OS cleans it up). Fixed now in commit 6e948f2ab9d32dde6ed854c3e5040d4afb5e169c. Thanks for reporting!
No problem, I'm glad I could help. I was using version 1.1 btw
When I tried to close the application, a segmentation fault happened.
Coredump: https://drive.google.com/folderview?id=0B63rdrZtwIE9fmxkT0xwVGRTeHd6QW1HSGtvU2tQR3NYNGhDX2J2TU96aVhkdzg3OG9sZUU&usp=sharing
BTW, it couldn't display any imagefiles or videos while running.