Le 04/03/2016 19:41, William F Pokorny a écrit :
> On 03/04/2016 01:22 PM, clipka wrote:
>> Am 04.03.2016 um 19:01 schrieb Le_Forgeron:
>>> Le 04/03/2016 17:22, William F Pokorny a écrit :
>> ...
>>>> Same here. The patch disappears in 3.7.1-alpha.8499454 while it works in
3.7.0-stable.
>>>
>>> Testing 3.7.1-alpha.8503825.unofficial, the object is there, same as with stable
version.
>>
>> While I did my own testing with 3.7.1-alpha.8503825 as well, I'd be
>> quite surprised if any of the changes since alpha.8499454 had fixed it.
>> They appear to be as unrelated as I could possibly imagine.
>>
> Think you are correct. I just pulled and compiled 3.7.1-alpha.8503825 on seeing
Jérôme at a newer version, but still nothing (no ray patch intersections are found).
So maybe a 14.04 vs 15.1 difference ?
> 
> My compiler is g++ 4.8.
> 


Nope, even with a produced "right" picture, valgrind reports a definitive problem of
uninitialised data.

Just ignore the syscall param write, the interesting parts seem to be in bezier.cpp


I presume even windows get the same problem if you have some auditing tools on it.

And using the same valgrind on the stable version: no such issue.


It's new, it's fresh, it's hidden and unreliable, due to the memory content.

Post a reply to this message

Attachments:
Download 'memcheck2.txt' (48 KB)