POV-Ray : Newsgroups : povray.beta-test : problem with +D option at specific output file dimensions : Re: problem with +D option at specific output file dimensions Server Time
30 Apr 2024 19:10:34 EDT (-0400)
  Re: problem with +D option at specific output file dimensions  
From: Le Forgeron
Date: 14 Dec 2013 07:17:55
Message: <52ac4c73$1@news.povray.org>
Le 14/12/2013 12:38, William F Pokorny nous fit lire :
> OK. Not an expert, but it looks like the segfault happened in this run
> in thread 7 (SetPixelScaled in disp_sdl.cpp:353) :

What about thread 1 ? raise is not normal (neither is abort), for a
std::string operation. Can it be some buffer-overflow (with a gigantic
message to assign with operator=) ? Or a nullptr ?


Thread 1 (Thread 0x7f85a5b4e740 (LWP 11003)):
#0  0x00007f85a34d5425 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007f85a34d8b8b in abort () from /lib/x86_64-linux-gnu/libc.so.6
#2  0x00007f85a351339e in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#3  0x00007f85a351db96 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#4  0x00007f85a402dff6 in std::string::assign(std::string const&) ()
   from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#5  0x0000000000422f33 in operator= (__str=..., this=0x7fff16b88570)
    at /usr/include/c++/4.6/bits/basic_string.h:542
#6  vfe::vfeSession::GetNextCombinedMessage (this=0x196d870,
    Type=@0x7fff16b88580: vfe::vfeSession::mGenericStatus, Message=...)
    at vfesession.cpp:416
#7  0x0000000000440b72 in PrintStatus (session=0x196d870)
    at unix/unixconsole.cpp:226
#8  0x0000000000412c87 in main (argc=7, argv=0x1970518)
    at unix/unixconsole.cpp:566

Thread 7 is performing a poll(), waiting for some I/O on some file
descriptor (X11 (provider of SDL) use file descriptor to communicate
with the X11 server, aka your display), nothing that would crash it.

Nice job at getting such detailed information.


Post a reply to this message

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