On 02/13/2017 02:03 PM, clipka wrote:
>>
>> The specific trigger is a change in a find_axis() for loop where the
>> problem additions have been commented so things work:
>>
>>     for(i = first; i < last; i++)
>>     {
>>         bbox = &(Finite[i]->BBox);
>>
>>         if(bbox->lowerLeft[X] < mins[X])
>>             mins[X] = bbox->lowerLeft[X];
>>
>>         if(bbox->lowerLeft[X] + bbox->size[X] > maxs[X])
>>             maxs[X] = bbox->lowerLeft[X]; // + bbox->size[X]; // <--
>>
>>         if(bbox->lowerLeft[Y] < mins[Y])
>>             mins[Y] = bbox->lowerLeft[Y];
>>
>>         if(bbox->lowerLeft[Y] + bbox->size[Y] > maxs[Y])
>>             maxs[Y] = bbox->lowerLeft[Y]; // + bbox->size[Y]; // <--
>>
>>         if(bbox->lowerLeft[Z] < mins[Z])
>>             mins[Z] = bbox->lowerLeft[Z];
>>
>>         if(bbox->lowerLeft[Z] + bbox->size[Z] > maxs[Z])
>>             maxs[Z] = bbox->lowerLeft[Z]; // + bbox->size[Z]; // <--
>>     }
>
> What exactly makes you think these changes have anything to do with the
> segfault?
>

:-) Nothing except running the code as above makes the seg fault go 
away. It doesn't make sense to me either.

>
> Good question. I haven't been able to trigger an error on Windows
> either; neither with frame 4 (as suggested by the ini file provided by
> Dick) nor with any frame from 1 to 153. And I don't think it makes much
> sense to try the remaining 3000 frames of the animation.
>
> One thing we might do is to go further back in the Git history, but use
> the newer `find_axis()` code, in the hope that we might find the commit
> that /really/ broke things.
>

A good suggestion - thanks.

Let me try again to get some kind of debug version which seg faults - 
otherwise...

(Saw your comment Dick & thought I tried -O3 with debug symbols, but was 
running lots of various compiles this morning so maybe I slipped up.)

Bill P.

Post a reply to this message