POV-Ray : Newsgroups : povray.beta-test : adc_bailout and max_trace_level Server Time
5 Nov 2024 03:14:41 EST (-0500)
  adc_bailout and max_trace_level (Message 1 to 6 of 6)  
From: Simon
Subject: adc_bailout and max_trace_level
Date: 15 Sep 2001 10:27:50
Message: <3ba36566@news.povray.org>
POV-Ray v3.5b2 Windows 98 Celeron 433 64 mb SDRam

POV-Ray crashes when adc_bailout is 0 and max_trace_level is higher as 309

global_settings{
  max_trace_level 310
  adc_bailout 0}

camera{
  location <0,0,-10>
  look_at <0,0,0>}

plane{x,3
  finish{reflection{1}}}

plane{x,-3
  finish{reflection{1}}}


Post a reply to this message

From: Ken
Subject: Re: adc_bailout and max_trace_level
Date: 15 Sep 2001 10:34:01
Message: <3BA367DA.689F0959@pacbell.net>
Simon wrote:
> 
> POV-Ray v3.5b2 Windows 98 Celeron 433 64 mb SDRam
> 
> POV-Ray crashes when adc_bailout is 0 and max_trace_level is higher as 309

Confirmed. Win98 POV-Ray v3.5.b2 Athlon 950 256 Ram

PVENGINE caused a stack fault in module PVENGINE.EXE at 015f:0043f0b1.
Registers:
EAX=01b02324 CS=015f EIP=0043f0b1 EFLGS=00010246
EBX=00000000 SS=0167 ESP=01b01a34 EBP=01b021e8
ECX=00000000 DS=0167 ESI=009bb4b8 FS=3a27
EDX=01b02350 ES=0167 EDI=00000000 GS=0000
Bytes at CS:EIP:
53 89 08 89 48 04 89 48 08 89 48 0c 89 48 10 39 
Stack dump:
00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000 


-- 
Ken Tyler - POV-Ray Technical Assistance Group


Post a reply to this message

From: Warp
Subject: Re: adc_bailout and max_trace_level
Date: 15 Sep 2001 18:03:45
Message: <3ba3d041@news.povray.org>
This could be a compiler-related problem, ie. there are no bugs in the
POV-Ray source code, but the problem is generated by the compiler. Some
compilers allocate a laughably small recursion stack for functions. The size
of this stack can be usually increased by a linker parameter or something
similar.

-- 
#macro N(D,I)#if(I<6)cylinder{M()#local D[I]=div(D[I],104);M().5,2pigment{
rgb M()}}N(D,(D[I]>99?I:I+1))#end#end#macro M()<mod(D[I],13)-6,mod(div(D[I
],13),8)-3,10>#end blob{N(array[6]{11117333955,
7382340,3358,3900569407,970,4254934330},0)}//                     - Warp -


Post a reply to this message

From: Ron Parker
Subject: Re: adc_bailout and max_trace_level
Date: 17 Sep 2001 16:04:11
Message: <slrn9qclpt.l3s.ron.parker@fwi.com>
On 15 Sep 2001 18:03:45 -0400, Warp wrote:
>  This could be a compiler-related problem, ie. there are no bugs in the
>POV-Ray source code, but the problem is generated by the compiler. Some
>compilers allocate a laughably small recursion stack for functions. The size
>of this stack can be usually increased by a linker parameter or something
>similar.

With Windows 32-bit code, it can even be increased after the fact by an
appropriate utility.

-- 
#macro R(L P)sphere{L F}cylinder{L P F}#end#macro P(V)merge{R(z+a z)R(-z a-z)R(a
-z-z-z a+z)torus{1F clipped_by{plane{a 0}}}translate V}#end#macro Z(a F T)merge{
P(z+a)P(z-a)R(-z-z-x a)pigment{rgbf 1}hollow interior{media{emission 3-T}}}#end 
Z(-x-x.2x)camera{location z*-10rotate x*90normal{bumps.02scale.05}}


Post a reply to this message

From: Thorsten Froehlich
Subject: Re: adc_bailout and max_trace_level
Date: 17 Sep 2001 16:41:44
Message: <3ba66008@news.povray.org>
In article <slr### [at] fwicom> , ron### [at] povrayorg (Ron
Parker) wrote:

> With Windows 32-bit code, it can even be increased after the fact by an
> appropriate utility.

Same on Macs (all one needs is ResEdit), and for threads it is even easier
as the stack size is set at run time when a new thread is created (I assume
the same is true on Windows).  BTW, the current Mac core code thread stack
size is 600 KB, what is the POV-Ray for Windows stack size?


    Thorsten


____________________________________________________
Thorsten Froehlich, Duisburg, Germany
e-mail: tho### [at] trfde

Visit POV-Ray on the web: http://mac.povray.org


Post a reply to this message

From: Ron Parker
Subject: Re: adc_bailout and max_trace_level
Date: 17 Sep 2001 16:59:23
Message: <slrn9qcp1d.l48.ron.parker@fwi.com>
On Mon, 17 Sep 2001 16:41:28 -0400, Thorsten Froehlich wrote:
>In article <slr### [at] fwicom> , ron### [at] povrayorg (Ron
>Parker) wrote:
>
>> With Windows 32-bit code, it can even be increased after the fact by an
>> appropriate utility.
>
>Same on Macs (all one needs is ResEdit), and for threads it is even easier
>as the stack size is set at run time when a new thread is created (I assume
>the same is true on Windows).  BTW, the current Mac core code thread stack
>size is 600 KB, what is the POV-Ray for Windows stack size?

(These are the values for a custom build of what was similar to beta 1;
since they're set by the IDE, I suspect all builds have these values.)

    100000 size of stack reserve
      1000 size of stack commit

Please note, those are hexadecimal numbers.  4K commit, 1M reserve.

--
#macro R(L P)sphere{L __}cylinder{L P __}#end#macro P(_1)union{R(z+_ z)R(-z _-z)
R(_-z*3_+z)torus{1__ clipped_by{plane{_ 0}}}translate z+_1}#end#macro S(_)9-(_1-
_)*(_1-_)#end#macro Z(_1 _ __)union{P(_)P(-_)R(y-z-1_)translate.1*_1-y*8pigment{
rgb<S(7)S(5)S(3)>}}#if(_1)Z(_1-__,_,__)#end#end Z(10x*-2,.2)camera{rotate x*90}


Post a reply to this message

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