[Bf-cycles] bad pointers with recent Cycles standalone build

Sergey Sharybin sergey.vfx at gmail.com
Mon Aug 29 09:45:35 CEST 2016


Several points:

1. Such errors are really difficult to give any meaningful suggestions
unless they are reproducable with official builds (like Blender). There are
lots of possibilities here starting from real issue in the code ending with
wrongly compiled dependencies.

2. There are fixes which were synchronized to standalone repo this morning
which solves some known crashes in subd code.

3. If that's recently introduced error you can easily isect the sources and
find out a buggy commit, so we can have a closer look on it.

On Mon, Aug 29, 2016 at 9:35 AM, Mohamed Sakr <3dsakr at gmail.com> wrote:

> Hi,
> I just grabbed the most recent build (18/8), I'm on Windows 10, VS2013,
> C++11
> there is a decent bug with the scene->mutex. (actually the bug is caused
> by the member DeviceScene dscene;)
> old build was running fine, new build got a problem which I'll explain
> what happens:
> memory is fine, so at any point in my DLL, if I check scene->mutex, memory
> is correct.
> now the problem comes when I try to access it:
> if (_session && _session->scene && _session->ready_to_reset() &&
> _session->scene->mutex.try_lock())
> here, scene->mutex.try_lock(), inside the function call, the mutex pointer
> is WRONG.
> after debugging, pointer is shifted by 2 indices (16 bytes)
> so outside the function, (scene->mutex._Mtx) is correct
> inside the function, *(&_Mtx + 2) is correct
> _Mtx alone is a corrupted memory, showing 0x0000...1
> any ideas?
> cheers,
> Mohamed Sakr
> _______________________________________________
> Bf-cycles mailing list
> Bf-cycles at blender.org
> https://lists.blender.org/mailman/listinfo/bf-cycles

With best regards, Sergey Sharybin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.blender.org/pipermail/bf-cycles/attachments/20160829/e3bd1e0c/attachment.htm 

More information about the Bf-cycles mailing list