Thorsten,

The problem is located here, according to gdb :

#0  0x1009c9a8 in buildsturm (ord=-25, sseq=0x7fffd7b8) at polysolv.cpp:273
273           *fp /= f;

Tracing backwards I found a very strange situation :

#0  0x1009c9a8 in buildsturm (ord=-25, sseq=0x7fffd7b8) at polysolv.cpp:273
#1  0x1009c91c in buildsturm (ord=-25, sseq=0x7fffd7b8) at polysolv.cpp:265
#2  0x1009bb68 in Solve_Polynomial (n=2147473744, c0=0x10100000,
r=0x7fffe0d8,
    sturm=269481264, epsilon=-0) at polysolv.cpp:1674
#3  0x10046b18 in intersect_lathe (Ray=0x7fffe898, Lathe=0x108c6fb0,
    Depth_Stack=0x10302f10) at lathe.cpp:440

look at #2, the value of n (2147473744), where all the calls to
Solve_Polynomial are done with values
2,4 or 6 in the function intersect_lathe. Notice the value of sturm
(269481264). Looks like a pretty serious corruption to me.

It's obvious that the corruption is not caused by a coding error , but by
some compiler setting. I'll try to build without the -mcpu setting.

Any further ideas ?

Jan Dewerchin





"Thorsten Froehlich" <tho### [at] trfde> wrote in message
news:3e1bf1c2@news.povray.org...
> In article <3e1be87e$1@news.povray.org> , "Jan Dewerchin"
> <jdw### [at] fabricom-idsbe> wrote:
>
> > It's as G4 as a G4 gets, i guess.
>
> Did you compile all libraries for the G4 as well?
>
> > I would like to stress that I get this problem ONLY with abyss.pov .
>
> How about using the debugger?  That will reveal where your compile
crashes.
>
> > Mind you, the same scene renders just fine with the windows version.
>
> Well, that is an official compile and obviously it has been tested with
all
> sample scenes...
>
>     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