POV-Ray : Newsgroups : povray.unix : segfault in povray : Re: segfault in povray Server Time
16 Apr 2024 02:53:31 EDT (-0400)
  Re: segfault in povray  
From: clipka
Date: 28 Jul 2014 22:11:26
Message: <53d702ce$1@news.povray.org>
Am 29.07.2014 03:25, schrieb jhu:
> clipka <ano### [at] anonymousorg> wrote:
>> Am 25.07.2014 09:06, schrieb Le_Forgeron:
>>> On 25/07/2014 02:38, wealthychef wrote:
>>>> I'm rendering a scene that does render OK in povray 3.7 RC6, and get this
>>>> badness:
>>>>
>>>> povray: backend/lighting/radiosity.cpp:324: virtual void
>>>> pov::RadiosityFunction::BeforeTile(int, unsigned int): Assertion `(pts >=
>>>> PRETRACE_FIRST) && (pts <= PRETRACE_MAX)' failed.
>>>> /usr/local/bin/povray3.7: line 11:  3097 Aborted                 (core dumped)
>>>> //usr/local/tools/povray-3.7.0/bin/povray.real "$@"
>>>>
>>>> ugh!  Is there a stable release candidate newer than RC6 I can try?
>>>> Thganks
>>>>
>>>>
>>> Known issue, in flyspray as #313 ( http://bugs.povray.org/ ).
>>>
>>> A correction has been suggested (and I implemented it on my forks), but
>>> it has not yet reach the official distribution.
>>
>> ... but a workaround has been implemented earlier.
>
> Instead of using an assertion, why not do a check if pts is within bounds, and
> if not then make pts equal to either min or max (whichever it's closest to)?

No - no, that's not the point. The assertion it there because pts 
shouldn't be out of bounds in the first place; it's a strong indicator 
that something's wrong elsewhere. (Not that it seems to break anything 
important -- which is why I haven't spent any time on futher digging yet 
-- but it's wrong nonetheless.)

After all, that's what assertions are for.


Post a reply to this message

Copyright 2003-2023 Persistence of Vision Raytracer Pty. Ltd.