I have finally gotten the Superpatch to compile properly, but if I use
an isosurface in a scene, it crashes after completing the render. It
generates the correct image file, but then drops into MacsBug and gives
this error:
PowerPC unmapped memory exception at 0D2EF480 remove_node+0000C
Any suggestions on where to look for the problem? I am fairly certain it
is in one of the isosurface files, because it seems to only happen when
they are used.

Post a reply to this message

That is an older version of the isosurface patch and an older version of
POV(3.02a). POV-Ray Unofficial(http://users.skynet.be/smellenbergh/) is
much more current-but still doesn't have all of what I need.

Post a reply to this message

On Fri, 01 Oct 1999 08:32:02 -0500, Chris Huff wrote:
>I have finally gotten the Superpatch to compile properly, but if I use
>an isosurface in a scene, it crashes after completing the render. It
>generates the correct image file, but then drops into MacsBug and gives
>this error:
>PowerPC unmapped memory exception at 0D2EF480 remove_node+0000C
>Any suggestions on where to look for the problem? I am fairly certain it
>is in one of the isosurface files, because it seems to only happen when
>they are used.
>

This happens for all isosurfaces, or for a specific scene?  Is it a
#declared object or is it specified directly?

Post a reply to this message

It is specified directly, and I haven't tested it enough to tell if it
happens for every isosurface. It happens for every one I have tried,
though(which is only a few).

Post a reply to this message

Chris Huff wrote:
> 
> That is an older version of the isosurface patch and an older version of
> POV(3.02a). POV-Ray Unofficial(http://users.skynet.be/smellenbergh/) is
> much more current-but still doesn't have all of what I need.

For some reason I had that described as a POV-Ray v3.1 version. This
has been corrected and I am sorry for wasting your time with it.

-- 
Ken Tyler
1100+ Povray, Graphics, 3D Rendering, and Raytracing Links:
http://home.pacbell.net/tylereng/index.html

Post a reply to this message

On Fri, 01 Oct 1999 08:43:53 -0500, Chris Huff wrote:
>It is specified directly, and I haven't tested it enough to tell if it
>happens for every isosurface. It happens for every one I have tried,
>though(which is only a few).

Do you have a source-level debugger so you can give me a stack traceback
along with source code for the three or four lines around each entry in
the stack?

Post a reply to this message

Well, the problem appears to be in the function Destroy_Function() in
F_FUNC.C. The crash does not occur if the POV_FREE() calls are commented
out, I will be working on narrowing it down further.
Oh, I do have a fairly advanced debugger, but I don't know how to use it
well. Is this something like what you were looking for?
  03A0CA80    PPC  0D2F06FC  Terminate_POV+00014
  03A0CA40    PPC  0D2F0864  close_all+000F8
  03A0CA00    PPC  0D2F2178  Destroy_All_Functions+0002C
  03A0C9C0    PPC  0D2F2254  Destroy_Function+00090

Post a reply to this message

Ok, I narrowed it down to the line
      if (Func->pnum >0) POV_FREE (Func->parm);
in Destroy_Function. If this line is commented out, the error doesn't
appear.
I think commenting this out causes a memory leak, however, the error
might be appearing because this has already been freed. I will be
studying the code some more, and running more tests...

Post a reply to this message

On Fri, 01 Oct 1999 20:24:58 -0500, Chris Huff wrote:
>Ok, I narrowed it down to the line
>      if (Func->pnum >0) POV_FREE (Func->parm);
>in Destroy_Function. If this line is commented out, the error doesn't
>appear.
>I think commenting this out causes a memory leak, however, the error
>might be appearing because this has already been freed. I will be
>studying the code some more, and running more tests...


It might also be appearing because under some unknown circumstances it
didn't get allocated, but I haven't gotten a chance to look at the code
yet to see if that's the case.

Post a reply to this message