POV-Ray : Newsgroups : povray.beta-test : So I managed to recreate the segfault... Server Time
28 Jul 2024 14:32:33 EDT (-0400)
  So I managed to recreate the segfault... (Message 1 to 2 of 2)  
From: clipka
Subject: So I managed to recreate the segfault...
Date: 26 Jan 2009 18:55:01
Message: <web.497e48b7f49e5fc3122a8da90@news.povray.org>
At last, POV has segfaulted in balcony.pov again! This time with coredump
enabled.

Let's see what gdb has to say:

    Core was generated by `povray -D -O~reference-output-exp.png render.ini`
    Program terminated with signal 11, Segmentation fault.

Uh-huh... so far nothing new... okay, tell me, wise gdb, *where* and *why* did
it segfault? Let's see:

    #0  00x00000000005b0c83 in ?? ()

Duh. Why do I get the feeling that this is *not* where the error actually
originated...?

Well, how about a stack trace then?

    (gdb) bt
    #0  0x000000000005b0c83 in ?? ()
    Cannot access memory at address 0x430030d8

Great. That would have been too easy, wouldn't it?

Blood-stained excrements of a male bovine.

Chris, or someone else with access to the source code - can someone please check
whether I might have made any stupid blunder in the implementation of the "trace
ticket" mechanism? It's currently the hottest candidate for causing (or
triggering) the trouble.

Anyone with expertise about whether this could actually be the symptom of a
stack overflow?


Post a reply to this message

From: Warp
Subject: Re: So I managed to recreate the segfault...
Date: 26 Jan 2009 19:14:31
Message: <497e51e7@news.povray.org>
clipka <nomail@nomail> wrote:
>     (gdb) bt
>     #0  0x000000000005b0c83 in ?? ()
>     Cannot access memory at address 0x430030d8

  Compiler optimizations tend to cause these things... (or a million of
other things as well)

-- 
                                                          - Warp


Post a reply to this message

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