On 12/12/2013 12:25 PM, James Dietrich wrote:
> Hello,
>
> http://wiki.povray.org/content/HowTo:Make_A_Bug_Report instructed me to come
> here first before submitting a bug report. Please let me know if I should submit
> this to the bug tracker.
>
> When I perform a render with this command line:
> povray +W2596 +H1003 +Ispiral.pov +Ospiral.png +D
> it fails every time in one of several ways:
>   -> a segmentation fault
>   -> aborted by xcb (example given below)
>   -> aborted by glibc (example given below)
>   -> apparent deadlock (render does not complete and povray process has to be
> killed with kill -9)
I have confirmed this coredump with RC7 (been busy so haven't been able 
to grab newer code) but I don't have a version compiled with debug 
symbols so not much more help than what James has already posted.

I'm running Ubuntu 12.01 on a monitor with the same native resolution of 
1980 by 1200.

Segmentation fault (core dumped)ls (92%) <-- % finished varies with 
small example James posted.

I captured a core file an tried to look at it with gdb.

(gdb) bt
#0  0x0000000000417745 in ?? ()
#1  0x00000000005ac499 in ?? ()
#2  0x00000000004559d4 in ?? ()
#3  0x0000000000598973 in ?? ()
#4  0x00000000005ebabe in ?? ()
#5  0x00000000005b5c63 in ?? ()
#6  0x00000000005b891e in ?? ()
#7  0x0000000000421c7f in ?? ()
#8  0x00007fcfffb04ce9 in thread_proxy ()
    from /usr/lib/libboost_thread.so.1.46.1
#9  0x00007fcfff0d0e9a in start_thread ()
    from /lib/x86_64-linux-gnu/libpthread.so.0
#10 0x00007fcffedfd3fd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#11 0x0000000000000000 in ?? ()

I tried this with one thread and oddly that works fine.

If I run an isosurface taking a lot longer to render I see a dump more 
like the first James posted starting with:

==== [Rendering...] ========================================================
*** glibc detected *** povray: munmap_chunk(): invalid pointer: 
0x00007fd40c1c37f0 ***
======= Backtrace: =========
/lib/x86_64-linux-gnu/libc.so.6(+0x7eb96)[0x7fd41dc47b96]
povray[0x5ac3c2]
povray[0x4559d4]
povray[0x598973]
povray[0x5ebabe]
povray[0x5b5c63]
povray[0x5b891e]
povray[0x421c7f]
/usr/lib/libboost_thread.so.1.46.1(thread_proxy+0x69)[0x7fd41e9c4ce9]
/lib/x86_64-linux-gnu/libpthread.so.0(+0x7e9a)[0x7fd41df90e9a]
/lib/x86_64-linux-gnu/libc.so.6(clone+0x6d)[0x7fd41dcbd3fd]
======= Memory map: ========
....

I am very curious James, what led you to the odd render resolution?

Aside: Newer versions of the boost thread library are available and 
yours at 1.49.0 is newer than mine. I've had no reason to date to try 
them. There are also some boost and pthread options during configuration 
many use to get clean builds, but again I've not had reason myself to 
try them.

Sorry not more help. If I get time this weekend, I'll try recompiling 
for debugging so the backtrace is perhaps more meaningful.
Bill P.

Post a reply to this message