[DXXR 0.58.1] segfaults on the RPi
#10
Maybe valgrind just misses the update of the texture handle with glGenTextures(), but what confuses me: even if it does, the value was first initialized to zero outside of any libs. Running with --track-origins=yes just gives me
Code:
==7663==  Uninitialised value was created by a heap allocation
==7663==    at 0x4835978: malloc (in /usr/lib/valgrind/vgpreload_memcheck-arm-linux.so)
which is not really helpful after all...
"Perfection is attained not when there is nothing more to add, but when there is nothing more to remove." -- Antoine de Saint Exupéry
Reply


Messages In This Thread
[DXXR 0.58.1] segfaults on the RPi - by derhass - 08-10-2013, 06:05 PM
Re: [DXXR 0.58.1] segfaults on the RPi - by zico - 08-10-2013, 06:23 PM
Re: [DXXR 0.58.1] segfaults on the RPi - by Kp - 08-10-2013, 06:28 PM
Re: [DXXR 0.58.1] segfaults on the RPi - by zico - 08-10-2013, 06:57 PM
Re: [DXXR 0.58.1] segfaults on the RPi - by zico - 08-10-2013, 07:49 PM
Re: [DXXR 0.58.1] segfaults on the RPi - by zico - 08-10-2013, 08:32 PM
Re: [DXXR 0.58.1] segfaults on the RPi - by derhass - 08-10-2013, 08:48 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)