POV-Ray : Newsgroups : povray.bugreports : 3.7RC3 animation error (64 bit, linux) : Re: 3.7RC3 animation error (64 bit, linux) Server Time
3 May 2024 04:18:51 EDT (-0400)
  Re: 3.7RC3 animation error (64 bit, linux)  
From: cab15625
Date: 16 May 2011 12:40:00
Message: <web.4dd152fba5d5536cb78589070@news.povray.org>
Le_Forgeron <lef### [at] freefr> wrote:
> Le 13/05/2011 20:36, cab15625 a écrit :
> > OK, I've tried a couple of different compile flag combinations, and I still get
> > the crash with my system.
> >
> > So, I tried to compile with debugging enabled.
> >
> > Running in a debugger shows that segfault occurs in disp_sdl.cpp at line 345
> >
> > the debugger is claiming that the int "ofs" used as an index has been "optimized
> > out".
> >
> > ofs is set in the previous line by
> >
> > unsigned int ofs = ix + iy * m_display->w;
> >
> > So, my question now is, does this occur as a result of a compiler error, or is
> > it a problem with something else.
> >
> > Note 1: As a matter of curiosity I also ran the test without the display
> > enabled.  Running povray with "-d" rather than "+d" results in a successful
> > render of all frames.
> >
> > Note 2: I thought I had compiled without optimization, but apparently I made a
> > typo when running configure.
> >
> >
> To compile without optimisation is harder than removing the "-s -O3" flags.
> By default gcc is -O2, so removing optimisation requires to use "-O0"
> (Oscar Zero)
>
> I'm very interested in this issue.
>
> --
> Software is like dirt - it costs time and money to change it and move it
> around.
>
> Just because you can't see it, it doesn't weigh anything,
> and you can't drill a hole in it and stick a rivet into it doesn't mean
> it's free.

I'm not sure how to proceed from here.  If I render with display turned off,
everything works fine.  If I render with display turned on, but small frames
(320x320) everything works fine.  If I render large frames (800x800) with
display turned on, the SDL code used to make displays work in X seems to crash
due to problems with optimization.  Is there anything that I can try to narrow
down the problem?

Would changing the CFLAGS environment variable be sufficient to override what
the POV-Ray compile does?


Post a reply to this message

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