 |
|
|
|
|
|
| |
| |
|
|
|
|
| |
| |
|
|
POV-Ray 3.7.1 has now officially entered public beta testing phase.
Source code and Windows binaries are available on GitHub:
https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
(beta.1 was an internal release only.)
The beta version is designed to install in its own dedicated directory,
and live happily alongside an existing 3.7 installation.
Happy testing!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka wrote on 11/01/2017 06:59:
> POV-Ray 3.7.1 has now officially entered public beta testing phase.
> Source code and Windows binaries are available on GitHub:
>
> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
>
> (beta.1 was an internal release only.)
>
> The beta version is designed to install in its own dedicated directory,
> and live happily alongside an existing 3.7 installation.
>
> Happy testing!
>
Very well! Thank you for your work,
Paolo
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Does not work! Linux Mageia 5 :(
***INITIALIZING***
png
***-STARTING-***
/usr/bin/povray
Povray found
b'Persistence of Vision(tm) Ray Tracer Version 3.7.1-beta.2.unofficial (g++
4.9.2
@ x86_64-unknown-linux-gnu)
This is an unofficial version compiled by:
LanuHum
The POV-Ray Team is not responsible for supporting this version.
POV-Ray is based on DKBTrace 2.12 by David K. Buck & Aaron A. Collins
Copyright 1991-2017 Persistence of Vision Raytracer Pty. Ltd.
Primary POV-Ray 3.7 Architects/Developers: (Alphabetically)
Chris Cason Thorsten Froehlich Christoph Lipka
With Assistance F'With Assistance F'b'rom: (Alphabetically)
Nicolas Calimet Jerome Grimbert James Holsenback Christoph Hormann
Nathan Kopp Juha Nieminen William F. Pokorny
Past Contributors: (Alphabetically)
Steve Anger Eric Barish Dieter Bayer David K. Buck
Nicolas Calimet Chris Cason Aaron A. Collins Chris Dailey
Steve Demlow Andreas Dilger Alexander Enzmann Dan Farmer
Thorsten Froehlich Mark Gordon Jerome Grimber' Thorsten Froehlich
Mark Gordon Jerome Grimber'b't James Holsenback
Christoph Hormann Mike Hough Chris Huff Kari Kivisalo
Nathan Kopp Lutz Kretzschmar Christoph Lipka Jochen Lippert
Pascal Massimino Jim McElhiney Douglas Muir Juha Nieminen
Ron Parker William F. Pokorny Bill Pulver Eduard Schwan
Wlodzimierz Skiba Robert Skinner Yvo Smellenbergh Zsolt Szalavari
Scott Taylor Massimo Valentini Timothy Wegner Drew Wel'***
Error in `/usr/bin/povray': free(): invalid next size (fast): 0x00007f2ff0017120
***
======= Backtrace: =========
/lib64/libc.so.6(+0x7238e)[0x7f30092d638e]
/lib64/libc.so.6(+0x7a0c8)[0x7f30092de0c8]
/lib64/libc.so.6(cfree+0x48)[0x7f30092e1798]
/usr/bin/povray[0x5ae899]
/usr/bin/povray[0x5af82a]
/usr/bin/povray[0x5b3d93]
/usr/bin/povray[0x5b817c]
/usr/bin/povray[0x5b4df5]
/usr/bin/povray[0x58f4a8]
/usr/bin/povray[0x58fd3c]
/usr/bin/povray[0x5125e5]
/lib64/libboost_thread.so.1.55.0(+0xde9a)[0x7f300a052e9a]
/lib64/libpthread.so.0(+0x75bd)[0x7f300ada35bd]
/lib64/libc.so.6(clone+0x6d)[0x7f300935b62d]
======= Memory map: ========
00400000-00709000 r-xp 00000000 08:01 466462
/usr/bin/povray
00909000-0090a000 r--p 00309000 08:01 466462
/usr/bin/povray
0090a000-0090f000 rw-p 0030a000 08:01 466462
/usr/bin/povray
0090f000-00973000 rw-p 00000000 00:00 0
01848000-01869000 rw-p 00000000 00:00 0 [heap]
7f2ff0000000-7f2ff0036000 rw-p 00000000 00:00 0
7f2ff0036000-7f2ff4000000 ---p 00000000 00:00 0
7f2ff8000000-7f2ff8049000 rw-p 00000000 00:00 0
7f2ff8049000-7f2ffc000000 ---p 00000000 00:00 0
7f2ffc000000-7f2ffc021000 rw-p 00000000 00:00 0
7f2ffc021000-7f3000000000 ---p 00000000 00:00 0
7f3000000000-7f3000021000 rw-p 00000000 00:00 0
7f3000021000-7f3004000000 ---p 00000000 00:00 0
7f30049c3000-7f30049c4000 ---p 00000000 00:00 0
7f30049c4000-7f30055a8000 rw-p 00000000 00:00 0
7f30055a8000-7f30055a9000 ---p 00000000 00:00 0
7f30055a9000-7f3005da9000 rw-p 00000000 00:00 0
7f3005da9000-7f3005daa000 ---p 00000000 00:00 0
7f3005daa000-7f30065aa000 rw-p 00000000 00:00 0
7f30065aa000-7f30065af000 r-xp 00000000 08:01 397575
/usr/lib64/libXdmcp.so.6.0.0
7f30065af000-7f30067ae000 ---p 00005000 08:01 397575
/usr/lib64/libXdmcp.so.6.0.0
7f30067ae000-7f30067af000 r--p 00004000 08:01 397575
/usr/lib64/libXdmcp.so.6.0.0
7f30067af000-7f30067b0000 rw-p 00005000 08:01 397575
/usr/lib64/libXdmcp.so.6.0.0
7f30067b0000-7f30067b2000 r-xp 00000000 08:01 397577
/usr/lib64/libXau.so.6.0.0
7f30067b2000-7f30069b2000 ---p 00002000 08:01 397577
/usr/lib64/libXau.so.6.0.0
7f30069b2000-7f30069b3000 r--p 00002000 08:01 397577
/usr/lib64/libXau.so.6.0.0
7f30069b3000-7f30069b4000 rw-p 00003000 08:01 397577
/usr/lib64/libXau.so.6.0.0
7f30069b4000-7f30069ba000 r-xp 00000000 08:01 402221
/usr/lib64/libgpm.so.2.1.0
7f30069ba000-7f3006bb9000 ---p 00006000 08:01 402221
/usr/lib64/libgpm.so.2.1.0
7f3006bb9000-7f3006bba000 r--p 00005000 08:01 402221
/usr/lib64/libgpm.so.2.1.0
7f3006bba000-7f3006bbb000 rw-p 00006000 08:01 402221
/usr/lib64/libgpm.so.2.1.0
7f3006bbb000-7f3006caf000 r-xp 00000000 08:01 402229
/usr/lib64/libslang.so.2.2.4
7f3006caf000-7f3006eaf000 ---p 000f4000 08:01 402229
/usr/lib64/libslang.so.2.2.4
7f3006eaf000-7f3006eb3000 r--p 000f4000 08:01 402229
/usr/lib64/libslang.so.2.2.4
7f3006eb3000-7f3006ecc000 rw-p 000f8000 08:01 402229
/usr/lib64/libslang.so.2.2.4
7f3006ecc000-7f3006f30000 rw-p 00000000 00:00 0
7f3006f30000-7f3006f38000 r-xp 00000000 08:01 402225
/usr/lib64/libgg.so.1.0.0
7f3006f38000-7f3007138000 ---p 00008000 08:01 402225
/usr/lib64/libgg.so.1.0.0
7f3007138000-7f3007139000 r--p 00008000 08:01 402225
/usr/lib64/libgg.so.1.0.0
7f3007139000-7f300713b000 rw-p 00009000 08:01 402225
/usr/lib64/libgg.so.1.0.0
7f300713b000-7f300713c000 rw-p 00000000 00:00 0
7f300713c000-7f3007159000 r-xp 00000000 08:01 402227
/usr/lib64/libgii.so.1.0.0
7f3007159000-7f3007359000 ---p 0001d000 08:01 402227
/usr/lib64/libgii.so.1.0.0
7f3007359000-7f300735a000 r--p 0001d000 08:01 402227
/usr/lib64/libgii.so.1.0.0
7f300735a000-7f300735d000 rw-p 0001e000 08:01 402227
/usr/lib64/libgii.so.1.0.0
7f300735d000-7f300736e000 r-xp 00000000 08:01 397583
/usr/lib64/libXext.so.6.4.0
7f300736e000-7f300756d000 ---p 00011000 08:01 397583
/usr/lib64/libXext.so.6.4.0
7f300756d000-7f300756e000 r--p 00010000 08:01 397583
/usr/lib64/libXext.so.6.4.0
7f300756e000-7f300756f000 rw-p 00011000 08:01 397583
/usr/lib64/libXext.so.6.4.0
7f300756f000-7f3007575000 r-xp 00000000 08:01 402223
/usr/lib64/libXxf86dga.so.1.0.0
7f3007575000-7f3007774000 ---p 00006000 08:01 402223
/usr/lib64/libXxf86dga.so.1.0.0
7f3007774000-7f3007775000 r--p 00005000 08:01 402223
/usr/lib64/libXxf86dga.so.1.0.0
7f3007775000-7f3007776000 rw-p 00006000 08:01 402223
/usr/lib64/libXxf86dga.so.1.0.0
7f3007776000-7f300779c000 r-xp 00000000 08:01 391753
/usr/lib64/libtinfo.so.5.9
7f300779c000-7f300799b000 ---p 00026000 08:01 391753
/usr/lib64/libtinfo.so.5.9
7f300799b000-7f300799f000 r--p 00025000 08:01 391753
/usr/lib64/libtinfo.so.5.9
7f300799f000-7f30079a0000 rw-p 00029000 08:01 391753
/usr/lib64/libtinfo.so.5.9
7f30079a0000-7f30079c6000 r-xp 00000000 08:01 391747
/usr/lib64/libncurses.so.5.9
7f30079c6000-7f3007bc6000 ---p 00026000 08:01 391747
/usr/lib64/libncurses.so.5.9
7f3007bc6000-7f3007bc7000 r--p 00026000 08:01 391747
/usr/lib64/libncurses.so.5.9
7f3007bc7000-7f3007bc8000 rw-p 00027000 08:01 391747
/usr/lib64/libncurses.so.5.9
7f3007bc8000-7f3007bec000 r-xp 00000000 08:01 397757
/usr/lib64/libdirect-1.7.so.5.0.0
7f3007bec000-7f3007dec000 ---p 00024000 08:01 397757
/usr/lib64/libdirect-1.7.so.5.0.0
7f3007dec000-7f3007ded000 r--p 00024000 08:01 397757
/usr/lib64/libdirect-1.7.so.5.0.0
7f3007ded000-7f3007dee000 rw-p 00025000 08:01 397757
/usr/lib64/libdirect-1.7.so.5.0.0
7f3007dee000-7f3007df0000 rw-p 00000000 00:00 0
7f3007df0000-7f3007dff000 r-xp 00000000 08:01 397761
/usr/lib64/libfusion-1.7.so.5.0.0
7f3007dff000-7f3007ffe000 ---p 0000f000 08:01 397761
/usr/lib64/libfusion-1.7.so.5.0.0
7f3007ffe000-7f3007fff000 r--p 0000e000 08:01 397761
/usr/lib64/libfusion-1.7.so.5.0.0
7f3007fff000-7f3008000000 rw-p 0000f000 08:01 397761
/usr/lib64/libfusion-1.7.so.5.0.0
7f3008000000-7f3008009000 r-xp 00000000 08:01 397670
/usr/lib64/libjbig.so.1.0.0
7f3008009000-7f3008208000 ---p 00009000 08:01 397670
/usr/lib64/libjbig.so.1.0.0
7f3008208000-7f3008209000 r--p 00008000 08:01 397670
/usr/lib64/libjbig.so.1.0.0
7f3008209000-7f300820c000 rw-p 00009000 08:01 397670
/usr/lib64/libjbig.so.1.0.0
7f300820c000-7f300823d000 r-xp 00000000 08:01 391927
/usr/lib64/liblzma.so.5.2.0
7f300823d000-7f300843c000 ---p 00031000 08:01 391927
/usr/lib64/liblzma.so.5.2.0
7f300843c000-7f300843d000 r--p 00030000 08:01 391927
/usr/lib64/liblzma.so.5.2.0
7f300843d000-7f300843e000 rw-p 00031000 08:01 391927
/usr/lib64/liblzma.so.5.2.0
7f300843e000-7f300845d000 r-xp 00000000 08:01 397578
/usr/lib64/libxcb.so.1.1.0
7f300845d000-7f300865c000 ---p 0001f000 08:01 397578
/usr/lib64/libxcb.so.1.1.0
7f300865c000-7f300865d000 r--p 0001e000 08:01 397578
/usr/lib64/libxcb.so.1.1.0
7f300865d000-7f300865e000 rw-p 0001f000 08:01 397578
/usr/lib64/libxcb.so.1.1.0
7f300865e000-7f3008661000 r-xp 00000000 08:01 397873
/usr/lib64/libuuid.so.1.3.0
7f3008661000-7f3008861000 ---p 00003000 08:01 397873
/usr/lib64/libuuid.so.1.3.0
7f3008861000-7f3008862000 r--p 00003000 08:01 397873
/usr/lib64/libuuid.so.1.3.0
7f3008862000-7f3008863000 rw-p 00004000 08:01 397873
/usr/lib64/libuuid.so.1.3.0
7f3008863000-7f300887e000 r-xp 00000000 08:01 402248
/usr/lib64/libaa.so.1.0.4
7f300887e000-7f3008a7d000 ---p 0001b000 08:01 402248
/usr/lib64/libaa.so.1.0.4
7f3008a7d000-7f3008a7f000 r--p 0001a000 08:01 402248
/usr/lib64/libaa.so.1.0.4
7f3008a7f000-7f3008a80000 rw-p 0001c000 08:01 402248
/usr/lib64/libaa.so.1.0.4
7f3008a80000-7f3008a82000 rw-p 00000000 00:00 0
7f3008a82000-7f3008b03000 r-xp 00000000 08:01 402453
/usr/lib64/libggi.so.2.0.2
7f3008b03000-7f3008d02000 ---p 00081000 08:01 402453
/usr/lib64/libggi.so.2.0.2
7f3008d02000-7f3008d03000 r--p 00080000 08:01 402453
/usr/lib64/libggi.so.2.0.2
7f3008d03000-7f3008d08000 rw-p 00081000 08:01 402453
/usr/lib64/libggi.so.2.0.2
7f3008d08000-7f3008d1e000 rw-p 00000000 00:00 0
7f3008d1e000-7f3008e53000 r-xp 00000000 08:01 397759
/usr/lib64/libdirectfb-1.7.so.5.0.0
7f3008e53000-7f3009052000 ---p 00135000 08:01 397759
/usr/lib64/libdirectfb-1.7.so.5.0.0
7f3009052000-7f3009059000 r--p 00134000 08:01 397759
/usr/lib64/libdirectfb-1.7.so.5.0.0
7f3009059000-7f3009060000 rw-p 0013b000 08:01 397759
/usr/lib64/libdirectfb-1.7.so.5.0.0
7f3009060000-7f3009063000 r-xp 00000000 08:01 416810
/usr/lib64/libdl-2.20.so
7f3009063000-7f3009262000 ---p 00003000 08:01 416810
/usr/lib64/libdl-2.20.so
7f3009262000-7f3009263000 r--p 00002000 08:01 416810
/usr/lib64/libdl-2.20.so
7f3009263000-7f3009264000 rw-p 00003000 08:01 416810
/usr/lib64/libdl-2.20.so
7f3009264000-7f300940e000 r-xp 00000000 08:01 391042
/usr/lib64/libc-2.20.so
7f300940e000-7f300960e000 ---p 001aa000 08:01 391042
/usr/lib64/libc-2.20.so
7f300960e000-7f3009612000 r--p 001aa000 08:01 391042
/usr/lib64/libc-2.20.so
7f3009612000-7f3009614000 rw-p 001ae000 08:01 391042
/usr/lib64/libc-2.20.so
7f3009614000-7f3009618000 rw-p 00000000 00:00 0
7f3009618000-7f300962e000 r-xp 00000000 08:01 391078
/usr/lib64/libgcc_s-4.9.2.so.1
7f300962e000-7f300982d000 ---p 00016000 08:01 391078
/usr/lib64/libgcc_s-4.9.2.so.1
7f300982d000-7f300982e000 r--p 00015000 08:01 391078
/usr/lib64/libgcc_s-4.9.2.so.1
7f300982e000-7f300982f000 rw-p 00016000 08:01 391078
/usr/lib64/libgcc_s-4.9.2.so.1
7f300982f000-7f3009934000 r-xp 00000000 08:01 416811
/usr/lib64/libm-2.20.so
7f3009934000-7f3009b33000 ---p 00105000 08:01 416811
/usr/lib64/libm-2.20.so
7f3009b33000-7f3009b34000 r--p 00104000 08:01 416811
/usr/lib64/libm-2.20.so
7f3009b34000-7f3009b35000 rw-p 00105000 08:01 416811
/usr/lib64/libm-2.20.so
7f3009b35000-7f3009c22000 r-xp 00000000 08:01 391631
/usr/lib64/libstdc++.so.6.0.20
7f3009c22000-7f3009e22000 ---p 000ed000 08:01 391631
/usr/lib64/libstdc++.so.6.0.20
7f3009e22000-7f3009e2a000 r--p 000ed000 08:01 391631
/usr/lib64/libstdc++.so.6.0.20
7f3009e2a000-7f3009e2c000 rw-p 000f5000 08:01 391631
/usr/lib64/libstdc++.so.6.0.20
7f3009e2c000-7f3009e41000 rw-p 00000000 00:00 0
7f3009e41000-7f3009e44000 r-xp 00000000 08:01 404257
/usr/lib64/libboost_system.so.1.55.0
7f3009e44000-7f300a043000 ---p 00003000 08:01 404257
/usr/lib64/libboost_system.so.1.55.0
7f300a043000-7f300a044000 r--p 00002000 08:01 404257
/usr/lib64/libboost_system.so.1.55.0
7f300a044000-7f300a045000 rw-p 00003000 08:01 404257
/usr/lib64/libboost_system.so.1.55.0
7f300a045000-7f300a05d000 r-xp 00000000 08:01 407355
/usr/lib64/libboost_thread.so.1.55.0
7f300a05d000-7f300a25c000 ---p 00018000 08:01 407355
/usr/lib64/libboost_thread.so.1.55.0
7f300a25c000-7f300a25e000 r--p 00017000 08:01 407355
/usr/lib64/libboost_thread.so.1.55.0
7f300a25e000-7f300a25f000 rw-p 00019000 08:01 407355
/usr/lib64/libboost_thread.so.1.55.0
7f300a25f000-7f300a266000 r-xp 00000000 08:01 416818
/usr/lib64/librt-2.20.so
7f300a266000-7f300a465000 ---p 00007000 08:01 416818
/usr/lib64/librt-2.20.so
7f300a465000-7f300a466000 r--p 00006000 08:01 416818
/usr/lib64/librt-2.20.so
7f300a466000-7f300a467000 rw-p 00007000 08:01 416818
/usr/lib64/librt-2.20.so
7f300a467000-7f300a480000 r-xp 00000000 08:01 391848
/usr/lib64/libz.so.1.2.8
7f300a480000-7f300a680000 ---p 00019000 08:01 391848
/usr/lib64/libz.so.1.2.8
7f300a680000-7f300a681000 r--p 00019000 08:01 391848
/usr/lib64/libz.so.1.2.8
7f300a681000-7f300a682000 rw-p 0001a000 08:01 391848
/usr/lib64/libz.so.1.2.8
7f300a682000-7f300a6db000 r-xp 00000000 08:01 416886
/usr/lib64/libpng16.so.16.25.0
7f300a6db000-7f300a8da000 ---p 00059000 08:01 416886
/usr/lib64/libpng16.so.16.25.0
7f300a8da000-7f300a8db000 r--p 00058000 08:01 416886
/usr/lib64/libpng16.so.16.25.0
7f300a8db000-7f300a8dc000 rw-p 00059000 08:01 416886
/usr/lib64/libpng16.so.16.25.0
7f300a8dc000-7f300a921000 r-xp 00000000 08:01 397661
/usr/lib64/libjpeg.so.8.0.2
7f300a921000-7f300ab20000 ---p 00045000 08:01 397661
/usr/lib64/libjpeg.so.8.0.2
7f300ab20000-7f300ab21000 r--p 00044000 08:01 397661
/usr/lib64/libjpeg.so.8.0.2
7f300ab21000-7f300ab22000 rw-p 00045000 08:01 397661
/usr/lib64/libjpeg.so.8.0.2
7f300ab22000-7f300ab32000 rw-p 00000000 00:00 0
7f300ab32000-7f300ab98000 r-xp 00000000 08:01 416887
/usr/lib64/libtiff.so.5.2.5
7f300ab98000-7f300ad97000 ---p 00066000 08:01 416887
/usr/lib64/libtiff.so.5.2.5
7f300ad97000-7f300ad9b000 r--p 00065000 08:01 416887
/usr/lib64/libtiff.so.5.2.5
7f300ad9b000-7f300ad9c000 rw-p 00069000 08:01 416887
/usr/lib64/libtiff.so.5.2.5
7f300ad9c000-7f300adb3000 r-xp 00000000 08:01 391068
/usr/lib64/libpthread-2.20.so
7f300adb3000-7f300afb2000 ---p 00017000 08:01 391068
/usr/lib64/libpthread-2.20.so
7f300afb2000-7f300afb3000 r--p 00016000 08:01 391068
/usr/lib64/libpthread-2.20.so
7f300afb3000-7f300afb4000 rw-p 00017000 08:01 391068
/usr/lib64/libpthread-2.20.so
7f300afb4000-7f300afb8000 rw-p 00000000 00:00 0
7f300afb8000-7f300afbe000 r-xp 00000000 08:01 398960
/usr/lib64/libIlmThread-2_2.so.12.0.0
7f300afbe000-7f300b1bd000 ---p 00006000 08:01 398960
/usr/lib64/libIlmThread-2_2.so.12.0.0
7f300b1bd000-7f300b1be000 r--p 00005000 08:01 398960
/usr/lib64/libIlmThread-2_2.so.12.0.0
7f300b1be000-7f300b1bf000 rw-p 00006000 08:01 398960
/usr/lib64/libIlmThread-2_2.so.12.0.0
7f300b1bf000-7f300b1c2000 r-xp 00000000 08:01 398958
/usr/lib64/libIexMath-2_2.so.12.0.0
7f300b1c2000-7f300b3c2000 ---p 00003000 08:01 398958
/usr/lib64/libIexMath-2_2.so.12.0.0
7f300b3c2000-7f300b3c3000 r--p 00003000 08:01 398958
/usr/lib64/libIexMath-2_2.so.12.0.0
7f300b3c3000-7f300b3c4000 rw-p 00004000 08:01 398958
/usr/lib64/libIexMath-2_2.so.12.0.0
7f300b3c4000-7f300b3e0000 r-xp 00000000 08:01 398956
/usr/lib64/libIex-2_2.so.12.0.0
7f300b3e0000-7f300b5e0000 ---p 0001c000 08:01 398956
/usr/lib64/libIex-2_2.so.12.0.0
7f300b5e0000-7f300b5e4000 r--p 0001c000 08:01 398956
/usr/lib64/libIex-2_2.so.12.0.0
7f300b5e4000-7f300b5e5000 rw-p 00020000 08:01 398956
/usr/lib64/libIex-2_2.so.12.0.0
7f300b5e5000-7f300b627000 r-xp 00000000 08:01 398954
/usr/lib64/libHalf.so.12.0.0
7f300b627000-7f300b826000 ---p 00042000 08:01 398954
/usr/lib64/libHalf.so.12.0.0
7f300b826000-7f300b827000 r--p 00041000 08:01 398954
/usr/lib64/libHalf.so.12.0.0
7f300b827000-7f300b828000 rw-p 00042000 08:01 398954
/usr/lib64/libHalf.so.12.0.0
7f300b828000-7f300b839000 r-xp 00000000 08:01 398962
/usr/lib64/libImath-2_2.so.12.0.0
7f300b839000-7f300ba38000 ---p 00011000 08:01 398962
/usr/lib64/libImath-2_2.so.12.0.0
7f300ba38000-7f300ba39000 r--p 00010000 08:01 398962
/usr/lib64/libImath-2_2.so.12.0.0
7f300ba39000-7f300ba3a000 rw-p 00011000 08:01 398962
/usr/lib64/libImath-2_2.so.12.0.0
7f300ba3a000-7f300bc08000 r-xp 00000000 08:01 398967
/usr/lib64/libIlmImf-2_2.so.22.0.0
7f300bc08000-7f300be07000 ---p 001ce000 08:01 398967
/usr/lib64/libIlmImf-2_2.so.22.0.0
7f300be07000-7f300be0b000 r--p 001cd000 08:01 398967
/usr/lib64/libIlmImf-2_2.so.22.0.0
7f300be0b000-7f300bf0e000 rw-p 001d1000 08:01 398967
/usr/lib64/libIlmImf-2_2.so.22.0.0
7f300bf0e000-7f300c047000 r-xp 00000000 08:01 397580
/usr/lib64/libX11.so.6.3.0
7f300c047000-7f300c246000 ---p 00139000 08:01 397580
/usr/lib64/libX11.so.6.3.0
7f300c246000-7f300c248000 r--p 00138000 08:01 397580
/usr/lib64/libX11.so.6.3.0
7f300c248000-7f300c24d000 rw-p 0013a000 08:01 397580
/usr/lib64/libX11.so.6.3.0
7f300c24d000-7f300c24e000 rw-p 00000000 00:00 0
7f300c24e000-7f300c265000 r-xp 00000000 08:01 397622
/usr/lib64/libICE.so.6.3.0
7f300c265000-7f300c465000 ---p 00017000 08:01 397622
/usr/lib64/libICE.so.6.3.0
7f300c465000-7f300c466000 r--p 00017000 08:01 397622
/usr/lib64/libICE.so.6.3.0
7f300c466000-7f300c467000 rw-p 00018000 08:01 397622
/usr/lib64/libICE.so.6.3.0
7f300c467000-7f300c46b000 rw-p 00000000 00:00 0
7f300c46b000-7f300c472000 r-xp 00000000 08:01 397660
/usr/lib64/libSM.so.6.0.1
7f300c472000-7f300c671000 ---p 00007000 08:01 397660
/usr/lib64/libSM.so.6.0.1
7f300c671000-7f300c672000 r--p 00006000 08:01 397660
/usr/lib64/libSM.so.6.0.1
7f300c672000-7f300c673000 rw-p 00007000 08:01 397660
/usr/lib64/libSM.so.6.0.1
7f300c673000-7f300c71b000 r-xp 00000000 08:01 402455
/usr/lib64/libSDL-1.2.so.0.11.4
7f300c71b000-7f300c91b000 ---p 000a8000 08:01 402455
/usr/lib64/libSDL-1.2.so.0.11.4
7f300c91b000-7f300c91c000 r--p 000a8000 08:01 402455
/usr/lib64/libSDL-1.2.so.0.11.4
7f300c91c000-7f300c91d000 rw-p 000a9000 08:01 402455
/usr/lib64/libSDL-1.2.so.0.11.4
7f300c91d000-7f300c94c000 rw-p 00000000 00:00 0
7f300c94c000-7f300c96c000 r-xp 00000000 08:01 391035
/usr/lib64/ld-2.20.so
7f300ca87000-7f300cb45000 rw-p 00000000 00:00 0
7f300cb46000-7f300cb48000 rw-p 00000000 00:00 0
7f300cb48000-7f300cb49000 ---p 00000000 00:00 0
7f300cb49000-7f300cb59000 rw-p 00000000 00:00 0
7f300cb59000-7f300cb5a000 ---p 00000000 00:00 0
7f300cb5a000-7f300cb6b000 rw-p 00000000 00:00 0
7f300cb6b000-7f300cb6c000 r--p 0001f000 08:01 391035
/usr/lib64/ld-2.20.so
7f300cb6c000-7f300cb6e000 rw-p 00020000 08:01 391035
/usr/lib64/ld-2.20.so
7fff070fc000-7fff0711d000 rw-p 00000000 00:00 0 [stack]
7fff071b2000-7fff071b4000 r--p 00000000 00:00 0 [vvar]
7fff071b4000-7fff071b6000 r-xp 00000000 00:00 0 [vdso]
ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0
[vsyscall]
***POV PROCESS FAILED : -6 ***
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 11.01.2017 um 15:50 schrieb LanuHum:
> Does not work! Linux Mageia 5 :(
Hmm... that's not /too/ much information to diagnose the problem...
>
> ***INITIALIZING***
> png
> ***-STARTING-***
> /usr/bin/povray
> Povray found
> b'Persistence of Vision(tm) Ray Tracer Version 3.7.1-beta.2.unofficial (g++
^^ What...
> 4.9.2
> @ x86_64-unknown-linux-gnu)
> This is an unofficial version compiled by:
> LanuHum
> The POV-Ray Team is not responsible for supporting this version.
>
> POV-Ray is based on DKBTrace 2.12 by David K. Buck & Aaron A. Collins
> Copyright 1991-2017 Persistence of Vision Raytracer Pty. Ltd.
>
> Primary POV-Ray 3.7 Architects/Developers: (Alphabetically)
> Chris Cason Thorsten Froehlich Christoph Lipka
>
> With Assistance F'With Assistance F'b'rom: (Alphabetically)
^^^^^^^^^^^^^^^^^^^^^ ... is...
> Nicolas Calimet Jerome Grimbert James Holsenback Christoph Hormann
> Nathan Kopp Juha Nieminen William F. Pokorny
>
> Past Contributors: (Alphabetically)
> Steve Anger Eric Barish Dieter Bayer David K. Buck
> Nicolas Calimet Chris Cason Aaron A. Collins Chris Dailey
> Steve Demlow Andreas Dilger Alexander Enzmann Dan Farmer
> Thorsten Froehlich Mark Gordon Jerome Grimber' Thorsten Froehlich
^^^^^^^^^^^^^^
> Mark Gordon Jerome Grimber'b't James Holsenback
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ ... all this clutter?
Could it be that you have a much more fundamental problem?
> Christoph Hormann Mike Hough Chris Huff Kari Kivisalo
> Nathan Kopp Lutz Kretzschmar Christoph Lipka Jochen Lippert
> Pascal Massimino Jim McElhiney Douglas Muir Juha Nieminen
> Ron Parker William F. Pokorny Bill Pulver Eduard Schwan
> Wlodzimierz Skiba Robert Skinner Yvo Smellenbergh Zsolt Szalavari
> Scott Taylor Massimo Valentini Timothy Wegner Drew Wel'***
>
> Error in `/usr/bin/povray': free(): invalid next size (fast): 0x00007f2ff0017120
> ***
> ======= Backtrace: =========
> /lib64/libc.so.6(+0x7238e)[0x7f30092d638e]
> /lib64/libc.so.6(+0x7a0c8)[0x7f30092de0c8]
> /lib64/libc.so.6(cfree+0x48)[0x7f30092e1798]
> /usr/bin/povray[0x5ae899]
> /usr/bin/povray[0x5af82a]
> /usr/bin/povray[0x5b3d93]
> /usr/bin/povray[0x5b817c]
> /usr/bin/povray[0x5b4df5]
> /usr/bin/povray[0x58f4a8]
> /usr/bin/povray[0x58fd3c]
> /usr/bin/povray[0x5125e5]
> /lib64/libboost_thread.so.1.55.0(+0xde9a)[0x7f300a052e9a]
> /lib64/libpthread.so.0(+0x75bd)[0x7f300ada35bd]
> /lib64/libc.so.6(clone+0x6d)[0x7f300935b62d]
Those addresses are of no help to us whatsoever. You'd have to compile
POV-Ray in a manner that the backtrace spits out function names and/or
file names and line numbers.
Also, I presume you're running POV-Ray from your Blender exporter. May I
suggest that you first try whether your build of 3.7.1-beta.2 runs
properly "stand-alone?"
If POV-Ray runs properly "stand-alone" with one of the provided sample
scenes, the next step would be to write the Blender export to a file,
and render that file by invoking POV-Ray "stand-alone".
If that fails, please provide us with the corresponding scene file, so
we can try to reproduce the problem on a Windows version, where we have
more debugging aids at our disposal.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 11.01.2017 um 06:59 schrieb clipka:
> The beta version is designed to install in its own dedicated directory,
> and live happily alongside an existing 3.7 installation.
Sorry, I should have mentioned that this applies only to the pre-built
binaries for Windows.
Users of Unixoid operating systems will need to specify corresponding
parameters to the ./configure script if they want to install the beta in
a separate directory; also, even then the beta may still share some
files and directories with the official version.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymous org> wrote:
> Am 11.01.2017 um 06:59 schrieb clipka:
>
> > The beta version is designed to install in its own dedicated directory,
> > and live happily alongside an existing 3.7 installation.
>
> Sorry, I should have mentioned that this applies only to the pre-built
> binaries for Windows.
>
> Users of Unixoid operating systems will need to specify corresponding
> parameters to the ./configure script if they want to install the beta in
> a separate directory; also, even then the beta may still share some
> files and directories with the official version.
I have another computer. AMD (1 kernel,1 thread) Povray has not been set. It was
the first compilation.
..../configure --prefix=/usr COMPILED_BY=Lanuhum no problem
make no problem
make install no problem
run povray - problem
Previously, I have a hundred times povray created from the source code.
Sometimes it was a configuration error.
This case (beta 2) is the first.
Now I installed 3.7.0 of the repository - no problem.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 11.01.2017 um 17:09 schrieb LanuHum:
> I have another computer. AMD (1 kernel,1 thread) Povray has not been set. It was
> the first compilation.
> ...../configure --prefix=/usr COMPILED_BY=Lanuhum no problem
> make no problem
> make install no problem
> run povray - problem
There is little we can do if all the feedback we get is "run povray -
problem".
/What/ problem?
Are you talking about the same symptoms as those mentioned in the other
post? If so, then see the response to that post for what additional
information might help us help you.
> Previously, I have a hundred times povray created from the source code.
> Sometimes it was a configuration error.
> This case (beta 2) is the first.
>
> Now I installed 3.7.0 of the repository - no problem.
It would be interesting to know whether the latest tagged alpha
(v3.7.1-alpha.8927145) works better than the beta. Since we've made only
very few changes to the source code since then, that would give us a
clear hint where to search for things that might be going wrong.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 11.01.2017 um 17:09 schrieb LanuHum:
> I have another computer. AMD (1 kernel,1 thread) Povray has not been set. It was
> the first compilation.
> ...../configure --prefix=/usr COMPILED_BY=Lanuhum no problem
> make no problem
> make install no problem
> run povray - problem
BTW, did you try "make check" before "make install"?
That should give an indication whether the problem is with the binary
itself, or with how it gets installed.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
clipka <ano### [at] anonymousorg> wrote:
> Am 11.01.2017 um 17:09 schrieb LanuHum:
>
> > I have another computer. AMD (1 kernel,1 thread) Povray has not been set. It was
> > the first compilation.
> > ...../configure --prefix=/usr COMPILED_BY=Lanuhum no problem
> > make no problem
> > make install no problem
> > run povray - problem
>
> There is little we can do if all the feedback we get is "run povray -
> problem".
>
> /What/ problem?
>
While only I see it:
Error in `/usr/bin/povray': free(): invalid next size (fast): 0x00007f2ff0017120
Creation of the source code takes a lot of time.
In my free time, I try more...
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
El 11/01/17 a las 06:59, clipka escribió:
> POV-Ray 3.7.1 has now officially entered public beta testing phase.
> Source code and Windows binaries are available on GitHub:
>
> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
>
> (beta.1 was an internal release only.)
>
> The beta version is designed to install in its own dedicated
> directory, and live happily alongside an existing 3.7 installation.
>
> Happy testing!
>
Compiled fine on Ubuntu 16.04, and seems to be working correctly with
a few existing scenes.
Thanks... this was maybe what I needed to get out of lethargy.
--
jaime
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 01/11/2017 07:02 PM, LanuHum wrote:
>>> I have another computer. AMD (1 kernel,1 thread) Povray has not been set. It was
>>> the first compilation.
>>> ...../configure --prefix=/usr COMPILED_BY=Lanuhum no problem
>>> make no problem
>>> make install no problem
>>> run povray - problem
>>
>> There is little we can do if all the feedback we get is "run povray -
>> problem".
>>
>> /What/ problem?
>>
>
> While only I see it:
> Error in `/usr/bin/povray': free(): invalid next size (fast): 0x00007f2ff0017120
$ man 3 mallopt
can give some help for trying to solve the problem...
> Creation of the source code takes a lot of time.
> In my free time, I try more...
>
>
>
>
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/01/2017 12:59 AM, clipka wrote:
> POV-Ray 3.7.1 has now officially entered public beta testing phase.
> Source code and Windows binaries are available on GitHub:
>
> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
>
> (beta.1 was an internal release only.)
>
> The beta version is designed to install in its own dedicated directory,
> and live happily alongside an existing 3.7 installation.
>
> Happy testing!
>
Will we be supporting WinXP 32 anymore?
A quick test suggests the render works, may have problems with editor.
More testing on Sunday morning local time.
Stephen S
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 11/01/2017 12:59 AM, clipka wrote:
> POV-Ray 3.7.1 has now officially entered public beta testing phase.
> Source code and Windows binaries are available on GitHub:
>
> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
>
> (beta.1 was an internal release only.)
>
> The beta version is designed to install in its own dedicated directory,
> and live happily alongside an existing 3.7 installation.
>
> Happy testing!
>
Will we be supporting WinXP 32 anymore?
A quick test suggests the render works, may have problems with editor.
More testing on Sunday morning local time.
Stephen S
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 13.01.2017 um 12:30 schrieb StephenS:
> On 11/01/2017 12:59 AM, clipka wrote:
>> POV-Ray 3.7.1 has now officially entered public beta testing phase.
>> Source code and Windows binaries are available on GitHub:
>>
>> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
>>
>> (beta.1 was an internal release only.)
>>
>> The beta version is designed to install in its own dedicated directory,
>> and live happily alongside an existing 3.7 installation.
>>
>> Happy testing!
>>
> Will we be supporting WinXP 32 anymore?
To all my current knowledge, the beta versions should work fine with XP.
In contrast to the alpha development binary-only builds, which were a
byproduct of automated build testing using a 3rd party service running
Visual Studio 2015 (which we couldn't get to spit out fully XP-comatible
binaries), the beta release was lovingly hand-crafted with good old
Visual Studio 2010, and we intend to do the same for all further 3.7.1
releases (betas, RCs and final release).
As for 32 bit, the installer contains all three binaries (32 bit, 32 bit
SSE2, and 64 bit) and should pick the one most appropriate for your machine.
Thus, should you encounter any problems with the beta on a 32 bit
Windows XP, please do let us know, as that would be unintentional.
> A quick test suggests the render works, may have problems with editor.
> More testing on Sunday morning local time.
Hm... I'll have to check with Chris whether he also used Visual Studio
2010 for the beta editor DLLs. (The beta does need its own version of
the DLLs to not interfere with an existing installation of 3.7.0 proper.
Other than that they should be interchangeable, though the beta DLLs
also contain some bugfixes.)
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 13.01.2017 um 13:30 schrieb clipka:
>> Will we be supporting WinXP 32 anymore?
...
>> A quick test suggests the render works, may have problems with editor.
>> More testing on Sunday morning local time.
>
> Hm... I'll have to check with Chris whether he also used Visual Studio
> 2010 for the beta editor DLLs. (The beta does need its own version of
> the DLLs to not interfere with an existing installation of 3.7.0 proper.
> Other than that they should be interchangeable, though the beta DLLs
> also contain some bugfixes.)
Chris just informed me that the editor DLLs have been built with Visual
Studio 2015, so they may or may not work on XP. Please do let us know
how you're faring.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 1/11/2017 12:59 AM, clipka wrote:
> POV-Ray 3.7.1 has now officially entered public beta testing phase.
> Source code and Windows binaries are available on GitHub:
>
> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
>
> (beta.1 was an internal release only.)
>
> The beta version is designed to install in its own dedicated directory,
> and live happily alongside an existing 3.7 installation.
>
> Happy testing!
>
well since i'm not a doze user perhaps it's just me but ... this release
seems to be having trouble honoring the Display = On option in the
master povray.ini file as well as having it in a povray.ini file in the
directory that the povray sdl file resides. In order to get a render
display i have to add +d in toolbar command line. btw: it (beta) is
reading all the other options (library path) options that i have in the
master povray.ini file
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 1/14/2017 9:20 AM, Jim Holsenback wrote:
> On 1/11/2017 12:59 AM, clipka wrote:
>> POV-Ray 3.7.1 has now officially entered public beta testing phase.
>> Source code and Windows binaries are available on GitHub:
>>
>> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
>>
>> (beta.1 was an internal release only.)
>>
>> The beta version is designed to install in its own dedicated directory,
>> and live happily alongside an existing 3.7 installation.
also stumbled upon a windows docs issue as well ...
in 3.2.4.1 output file type towards the bottom in the paragraph that
starts as: The Radiance Synthetic Imaging System ... there are two
external links: Radiance and OpenEXR. the Radiance link opens up the
web page inside the windows help viewer, the OpenEXR link opens up the
web age in default web /browser/ OpenEXR also appears as >>OpenEXR
also have a look from 2.5.6 --> to the bottom of that page there is a
mix of external links that exhibit the same behavior ... links that are
preceded by >> open up the web page in default web browser and the links
/without/ >> open web page inside the windows help viewer.
looked on the wiki and /all/ links markup are consistent and the nix
docs look fine (no >> anywhere) so i'm guessing it's regex issue in the
post processing that creates the doze docs
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 1/14/2017 10:28 AM, Jim Holsenback wrote:
> also have a look from 2.5.6 --> to the bottom of that page there
make that from 2.5.1
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 13/01/2017 2:50 PM, clipka wrote:
...
>> Hm... I'll have to check with Chris whether he also used Visual Studio
>> 2010 for the beta editor DLLs. (The beta does need its own version of
>> the DLLs to not interfere with an existing installation of 3.7.0 proper.
>> Other than that they should be interchangeable, though the beta DLLs
>> also contain some bugfixes.)
>
> Chris just informed me that the editor DLLs have been built with Visual
> Studio 2015, so they may or may not work on XP. Please do let us know
> how you're faring.
>
On WinVista home premium sp2 64-bit
All three POV-Ray application files run fine, no problems noted.
pvengine, pvengine-sse2, pvengine64(default).
On WinXP sp3 32-bit
pvengine and pvengine-sse2(default), POV-Ray runs fine, the editor has
problems opening a file tab.
From windows_explorer, click-hold-drag drop on editor works, new tab is
opened.
Menu/File/recently used list, select, new tab is opened.
Open icon, select file - open, no new tab is opened.
Menu/File/Open, select file - open, no new tab is opened.
Still working through some combinations.
Stephen S
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 14.01.2017 um 17:28 schrieb StephenS:
> On 13/01/2017 2:50 PM, clipka wrote:
> ....
>>> Hm... I'll have to check with Chris whether he also used Visual Studio
>>> 2010 for the beta editor DLLs. (The beta does need its own version of
>>> the DLLs to not interfere with an existing installation of 3.7.0 proper.
>>> Other than that they should be interchangeable, though the beta DLLs
>>> also contain some bugfixes.)
>>
>> Chris just informed me that the editor DLLs have been built with Visual
>> Studio 2015, so they may or may not work on XP. Please do let us know
>> how you're faring.
>>
> On WinVista home premium sp2 64-bit
> All three POV-Ray application files run fine, no problems noted.
> pvengine, pvengine-sse2, pvengine64(default).
>
> On WinXP sp3 32-bit
> pvengine and pvengine-sse2(default), POV-Ray runs fine, the editor has
> problems opening a file tab.
>
> From windows_explorer, click-hold-drag drop on editor works, new tab is
> opened.
> Menu/File/recently used list, select, new tab is opened.
> Open icon, select file - open, no new tab is opened.
> Menu/File/Open, select file - open, no new tab is opened.
>
> Still working through some combinations.
Don't bother -- it doesn't work properly on XP, that's all we need to
know for now. This is (in all likelyhood) not a matter of identifying
and fixing problematic source code, but of choosing the right build
settings (or even the right compiler version).
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 14.01.2017 um 15:20 schrieb Jim Holsenback:
> On 1/11/2017 12:59 AM, clipka wrote:
>> POV-Ray 3.7.1 has now officially entered public beta testing phase.
>> Source code and Windows binaries are available on GitHub:
>>
>> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
>>
>> (beta.1 was an internal release only.)
>>
>> The beta version is designed to install in its own dedicated directory,
>> and live happily alongside an existing 3.7 installation.
>>
>> Happy testing!
>>
> well since i'm not a doze user perhaps it's just me but ... this release
> seems to be having trouble honoring the Display = On option in the
> master povray.ini file as well as having it in a povray.ini file in the
> directory that the povray sdl file resides. In order to get a render
> display i have to add +d in toolbar command line. btw: it (beta) is
> reading all the other options (library path) options that i have in the
> master povray.ini file
Just to avoid confusion: I understand that you're not /normally/ a
Windows user, but are reporting your results of testing POV-Ray for
Windows - is that correct?
Are you testing on a genuine Windows machine, a virtual machine, or an
emulator (e.g. Wine)?
Also, which binary are you using - 32 bit, 32 bit SSE2, or 64 bit?
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 1/14/2017 1:42 PM, clipka wrote:
> Am 14.01.2017 um 15:20 schrieb Jim Holsenback:
>> On 1/11/2017 12:59 AM, clipka wrote:
>>> POV-Ray 3.7.1 has now officially entered public beta testing phase.
>>> Source code and Windows binaries are available on GitHub:
>>>
>>> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
>>>
>>> (beta.1 was an internal release only.)
>>>
>>> The beta version is designed to install in its own dedicated directory,
>>> and live happily alongside an existing 3.7 installation.
>>>
>>> Happy testing!
>>>
>> well since i'm not a doze user perhaps it's just me but ... this release
>> seems to be having trouble honoring the Display = On option in the
>> master povray.ini file as well as having it in a povray.ini file in the
>> directory that the povray sdl file resides. In order to get a render
>> display i have to add +d in toolbar command line. btw: it (beta) is
>> reading all the other options (library path) options that i have in the
>> master povray.ini file
adding that i installed beta down an alternate path (in my documents)
the 3.7 distribution lives in program files
>
> Just to avoid confusion: I understand that you're not /normally/ a
> Windows user, but are reporting your results of testing POV-Ray for
> Windows - is that correct?
you would be correct
>
> Are you testing on a genuine Windows machine, a virtual machine, or an
> emulator (e.g. Wine)?
the first one flavored windows 7 pro
>
> Also, which binary are you using - 32 bit, 32 bit SSE2, or 64 bit?
>
the later
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 14.01.2017 um 16:28 schrieb Jim Holsenback:
> On 1/14/2017 9:20 AM, Jim Holsenback wrote:
>> On 1/11/2017 12:59 AM, clipka wrote:
>>> POV-Ray 3.7.1 has now officially entered public beta testing phase.
>>> Source code and Windows binaries are available on GitHub:
>>>
>>> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
>>>
>>> (beta.1 was an internal release only.)
>>>
>>> The beta version is designed to install in its own dedicated directory,
>>> and live happily alongside an existing 3.7 installation.
>
> also stumbled upon a windows docs issue as well ...
>
> in 3.2.4.1 output file type towards the bottom in the paragraph that
> starts as: The Radiance Synthetic Imaging System ... there are two
> external links: Radiance and OpenEXR. the Radiance link opens up the
> web page inside the windows help viewer, the OpenEXR link opens up the
> web age in default web /browser/ OpenEXR also appears as >>OpenEXR
I can confirm that; more precisely, it's "»OpenEXR", where "»" is the
Unicode/ISO-Latin-1 character U+00BB, "RIGHT-POINTING DOUBLE ANGLE
QUOTATION MARK".
> also have a look from 2.5.6 --> to the bottom of that page there is a
> mix of external links that exhibit the same behavior ... links that are
> preceded by >> open up the web page in default web browser and the links
> /without/ >> open web page inside the windows help viewer.
>
> looked on the wiki and /all/ links markup are consistent and the nix
> docs look fine (no >> anywhere) so i'm guessing it's regex issue in the
> post processing that creates the doze docs
I can confirm that this is indeed created during post-processing for the
Windows HTML Help. From what I glean from the conversion script this is
intended to mark external links, but from the results I conclude that it
indeed fails to catch all instances.
From what I see, there are two cases in which the algorithm fails:
- Non-HTTP external links (e.g. "https://whatever").
- External links followed by more links (external or internal) on the
same HTML source line.
Looks like I can amend the script to catch those as well. If you
discover any instances that don't fall in either category, feel free to
holler out loud.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 14.01.2017 um 17:28 schrieb StephenS:
> On WinXP sp3 32-bit
> pvengine and pvengine-sse2(default), POV-Ray runs fine, the editor has
> problems opening a file tab.
Stephen, can you please try this experimental version of the editor
DLLs, and let us know whether it solves the XP issues:
www.povray.org/temp/povwin-3.7-beta-editor.exe
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 15/01/2017 12:55 AM, clipka wrote:
> Am 14.01.2017 um 17:28 schrieb StephenS:
>
>> On WinXP sp3 32-bit
>> pvengine and pvengine-sse2(default), POV-Ray runs fine, the editor has
>> problems opening a file tab.
>
> Stephen, can you please try this experimental version of the editor
> DLLs, and let us know whether it solves the XP issues:
>
> www.povray.org/temp/povwin-3.7-beta-editor.exe
>
Same problems.
Stephen S
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 15/01/2017 22:31, StephenS wrote:
> On 15/01/2017 12:55 AM, clipka wrote:
>> Am 14.01.2017 um 17:28 schrieb StephenS:
>>
>>> On WinXP sp3 32-bit
>>> pvengine and pvengine-sse2(default), POV-Ray runs fine, the editor has
>>> problems opening a file tab.
>>
>> Stephen, can you please try this experimental version of the editor
>> DLLs, and let us know whether it solves the XP issues:
>>
>> www.povray.org/temp/povwin-3.7-beta-editor.exe
>>
> Same problems.
Can you try dropping in, one by one, the editor DLL's from the 3.7.0
distribution (just copy & paste from the 3.7 bin directory) and find
out if/when the problem goes away? If so, changing which DLL fixed it?
Note: the 3.7.0 DLL's will pick up your 3.7.0 editor configuration,
this is to be expected.
-- Chris
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 15/01/2017 8:07 AM, Chris Cason wrote:
...
> Can you try dropping in, one by one, the editor DLL's from the 3.7.0
> distribution (just copy & paste from the 3.7 bin directory) and find
> out if/when the problem goes away? If so, changing which DLL fixed it?
>
> Note: the 3.7.0 DLL's will pick up your 3.7.0 editor configuration,
> this is to be expected.
>
> -- Chris
>
Replacing with only povcmax32-sse2.dll, made no change.
Reset files.
Replacing with only cmedit32-sse2.dll v3.7.0.0, fixed problems(open file
tabs).
Stephen S
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 15.01.2017 um 14:33 schrieb StephenS:
> On 15/01/2017 8:07 AM, Chris Cason wrote:
> ....
>> Can you try dropping in, one by one, the editor DLL's from the 3.7.0
>> distribution (just copy & paste from the 3.7 bin directory) and find
>> out if/when the problem goes away? If so, changing which DLL fixed it?
>>
>> Note: the 3.7.0 DLL's will pick up your 3.7.0 editor configuration,
>> this is to be expected.
>>
>> -- Chris
>>
> Replacing with only povcmax32-sse2.dll, made no change.
> Reset files.
> Replacing with only cmedit32-sse2.dll v3.7.0.0, fixed problems(open file
> tabs).
Can you please try replacing the cmedit32-sse2.dll with this one:
http://wiki.povray.org/clipka-files/cmedit32-sse2.dll
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 16/01/2017 8:08 PM, clipka wrote:
...
>> Replacing with only povcmax32-sse2.dll, made no change.
>> Reset files.
>> Replacing with only cmedit32-sse2.dll v3.7.0.0, fixed problems(open file
>> tabs).
>
> Can you please try replacing the cmedit32-sse2.dll with this one:
>
...
Looking good :-)
Files open in new tab.
Stephen S
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 17.01.2017 um 02:47 schrieb StephenS:
> On 16/01/2017 8:08 PM, clipka wrote:
> ....
>>> Replacing with only povcmax32-sse2.dll, made no change.
>>> Reset files.
>>> Replacing with only cmedit32-sse2.dll v3.7.0.0, fixed problems(open file
>>> tabs).
>>
>> Can you please try replacing the cmedit32-sse2.dll with this one:
>>
> ....
> Looking good :-)
> Files open in new tab.
Please do test exhaustively, and let us know if you come across any
peculiarities; after all the povcmax DLL you're using might still turn
out to be problematic as well.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 01/11/2017 01:59 AM, clipka wrote:
> POV-Ray 3.7.1 has now officially entered public beta testing phase.
> Source code and Windows binaries are available on GitHub:
>
> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
The file README.unix seems to be intended for POV-Ray 3.6.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2017-01-11 11:37 AM (-4), clipka wrote:
> Am 11.01.2017 um 15:50 schrieb LanuHum:
>> Does not work! Linux Mageia 5 :(
>> [snip]
>>
>> Error in `/usr/bin/povray': free(): invalid next size (fast): 0x00007f2ff0017120
>> ***
>> ======= Backtrace: =========
>> /lib64/libc.so.6(+0x7238e)[0x7f30092d638e]
>> /lib64/libc.so.6(+0x7a0c8)[0x7f30092de0c8]
>> /lib64/libc.so.6(cfree+0x48)[0x7f30092e1798]
>> /usr/bin/povray[0x5ae899]
>> /usr/bin/povray[0x5af82a]
>> /usr/bin/povray[0x5b3d93]
>> /usr/bin/povray[0x5b817c]
>> /usr/bin/povray[0x5b4df5]
>> /usr/bin/povray[0x58f4a8]
>> /usr/bin/povray[0x58fd3c]
>> /usr/bin/povray[0x5125e5]
>> /lib64/libboost_thread.so.1.55.0(+0xde9a)[0x7f300a052e9a]
>> /lib64/libpthread.so.0(+0x75bd)[0x7f300ada35bd]
>> /lib64/libc.so.6(clone+0x6d)[0x7f300935b62d]
I'm having the same trouble, though with different addresses. (I am not
getting any of the extraneous clutter that LanuHum posted, though.)
> Also, I presume you're running POV-Ray from your Blender exporter. May I
> suggest that you first try whether your build of 3.7.1-beta.2 runs
> properly "stand-alone?"
>
> If POV-Ray runs properly "stand-alone" with one of the provided sample
> scenes, the next step would be to write the Blender export to a file,
> and render that file by invoking POV-Ray "stand-alone".
I'm running it stand-alone.
> If that fails, please provide us with the corresponding scene file, so
> we can try to reproduce the problem on a Windows version, where we have
> more debugging aids at our disposal.
So far, it works for me on simple scenes, and crashes on complex files.
I'll see if I can reproduce it with a scene that doesn't require posting
half my library.
My distro is openSUSE 13.2.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2017-01-11 01:42 PM (-4), clipka wrote:
> Am 11.01.2017 um 17:09 schrieb LanuHum:
>
>> I have another computer. AMD (1 kernel,1 thread) Povray has not been set. It was
>> the first compilation.
>> ...../configure --prefix=/usr COMPILED_BY=Lanuhum no problem
>> make no problem
>> make install no problem
>> run povray - problem
>
> BTW, did you try "make check" before "make install"?
>
> That should give an indication whether the problem is with the binary
> itself, or with how it gets installed.
The cookies look delicious, but as I posted elsewhere, the installed
binary does work for some scenes.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2017-01-11 01:36 PM (-4), clipka wrote:
> It would be interesting to know whether the latest tagged alpha
> (v3.7.1-alpha.8927145) works better than the beta. Since we've made only
> very few changes to the source code since then, that would give us a
> clear hint where to search for things that might be going wrong.
GitHub still confuses me to no end. My latest alpha is 8917471, but
when I feel my way around GitHub, I cannot find any alpha version later
than 8737777.
8917471 works fine for me.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2017-02-01 05:57 PM (-4), Cousin Ricky wrote:
> On 2017-01-11 01:36 PM (-4), clipka wrote:
>> It would be interesting to know whether the latest tagged alpha
>> (v3.7.1-alpha.8927145) works better than the beta. Since we've made only
>> very few changes to the source code since then, that would give us a
>> clear hint where to search for things that might be going wrong.
>
> GitHub still confuses me to no end. My latest alpha is 8917471, but
> when I feel my way around GitHub, I cannot find any alpha version later
> than 8737777.
I just found 8927145.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2017-01-11 01:36 PM (-4), clipka wrote:
> It would be interesting to know whether the latest tagged alpha
> (v3.7.1-alpha.8927145) works better than the beta. Since we've made only
> very few changes to the source code since then, that would give us a
> clear hint where to search for things that might be going wrong.
Alpha.8927145 crashes. Alpha.8917471 runs splendidly.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2017-01-11 01:59 AM (-4), clipka wrote:
> POV-Ray 3.7.1 has now officially entered public beta testing phase.
> Source code and Windows binaries are available on GitHub:
>
> https://github.com/POV-Ray/povray/releases/tag/v3.7.1-beta.2
>
> (beta.1 was an internal release only.)
>
> The beta version is designed to install in its own dedicated directory,
> and live happily alongside an existing 3.7 installation.
>
> Happy testing!
The parser chokes on .ini files that are not in the current directory,
but are in the library path.
I wish I could say in what manner it choked, but the message was that
infuriatingly unspecific:
Problem with option setting
[Command line is echoed here.]
Failed to parse command-line option
Once again, if the parser had given a more helpful message, I could have
saved nearly an hour and a half figuring out what went wrong. I've been
complaining about this for five or six years now. PLEASE FIX THIS!
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2017-01-11 11:37 AM (-4), clipka wrote:
> If that fails, please provide us with the corresponding scene file, so
> we can try to reproduce the problem on a Windows version, where we have
> more debugging aids at our disposal.
The very first two scenes I tried failed in the same manner that
LanuHum's scene did. (They also failed with alpha.8927145.) Since
then, all of the scenes I've tried have rendered successfully.
Unfortunately, both of those first two scenes use an include file that
is more than 1 megabyte.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2017-01-11 11:37 AM (-4), clipka wrote:
> Those addresses are of no help to us whatsoever. You'd have to compile
> POV-Ray in a manner that the backtrace spits out function names and/or
> file names and line numbers.
Oh, I forgot to add: -version reports the compiler settings as:
Compilation settings:
Build architecture: x86_64-suse-linux-gnu
Built/Optimized for: x86_64-suse-linux-gnu (using -march=native)
Compiler vendor: gnu
Compiler version: g++ 4.8
Compiler flags: -pipe -Wno-multichar -Wno-write-strings
-fno-enforce-eh-specs -Wno-non-template-friend -s -O3 -ffast-math
-march=native -pthread
I don't know how to change the build scripts to include debugging
information.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 02/01/2017 07:49 PM, Cousin Ricky wrote:
> On 2017-01-11 11:37 AM (-4), clipka wrote:
>> If that fails, please provide us with the corresponding scene file, so
>> we can try to reproduce the problem on a Windows version, where we have
>> more debugging aids at our disposal.
>
> The very first two scenes I tried failed in the same manner that
> LanuHum's scene did. (They also failed with alpha.8927145.) Since
> then, all of the scenes I've tried have rendered successfully.
>
> Unfortunately, both of those first two scenes use an include file that
> is more than 1 megabyte.
Those first two scenes did not actually use the data in the 1 megabyte
file, so I dropped it, concatenated everything else into a single file,
then took a hatchet to the file.
Guess what? The one thing those two scenes had in common that all my
other tests did not was Greek text.
This appears to be the same charset utf8 bug that ThH uncovered. And
since LanuHum probably uses a lot of Cyrillic text, I'm guessing that
his is the same problem.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2017-02-01 10:26 PM (-4), Cousin Ricky wrote:
> Those first two scenes did not actually use the data in the 1 megabyte
> file, so I dropped it, concatenated everything else into a single file,
> then took a hatchet to the file.
Correction: only one of them didn't use the 1 MB file. I'm not thinking
straight today.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 02.02.2017 um 03:26 schrieb Cousin Ricky:
> On 02/01/2017 07:49 PM, Cousin Ricky wrote:
>> On 2017-01-11 11:37 AM (-4), clipka wrote:
>>> If that fails, please provide us with the corresponding scene file, so
>>> we can try to reproduce the problem on a Windows version, where we have
>>> more debugging aids at our disposal.
>>
>> The very first two scenes I tried failed in the same manner that
>> LanuHum's scene did. (They also failed with alpha.8927145.) Since
>> then, all of the scenes I've tried have rendered successfully.
>>
>> Unfortunately, both of those first two scenes use an include file that
>> is more than 1 megabyte.
>
> Those first two scenes did not actually use the data in the 1 megabyte
> file, so I dropped it, concatenated everything else into a single file,
> then took a hatchet to the file.
>
> Guess what? The one thing those two scenes had in common that all my
> other tests did not was Greek text.
>
> This appears to be the same charset utf8 bug that ThH uncovered. And
> since LanuHum probably uses a lot of Cyrillic text, I'm guessing that
> his is the same problem.
Sounds totally plausible.
If that is the case, then the next beta should fix it.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 01.02.2017 um 23:30 schrieb Cousin Ricky:
> On 2017-01-11 01:36 PM (-4), clipka wrote:
>> It would be interesting to know whether the latest tagged alpha
>> (v3.7.1-alpha.8927145) works better than the beta. Since we've made only
>> very few changes to the source code since then, that would give us a
>> clear hint where to search for things that might be going wrong.
>
> Alpha.8927145 crashes. Alpha.8917471 runs splendidly.
That fits well with the theory that it's the "utf8" bug you're experiencing.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
Am 02.02.2017 um 00:38 schrieb Cousin Ricky:
> The parser chokes on .ini files that are not in the current directory,
> but are in the library path.
>
> I wish I could say in what manner it choked, but the message was that
> infuriatingly unspecific:
>
> Problem with option setting
> [Command line is echoed here.]
> Failed to parse command-line option
>
> Once again, if the parser had given a more helpful message, I could have
> saved nearly an hour and a half figuring out what went wrong. I've been
> complaining about this for five or six years now. PLEASE FIX THIS!
This seems to be one of various shortcomings of my arch nemesis, the
"VFE" layer, which appears to provide no way whatsoever to pass on any
details why it rejects the command-line.
I've been gaining ground in my uphill battle against the VFE (my intent
being to get rid of it entirely), but it takes time, and this particular
corner of the battlefield isn't one of the strategic positions I'm
focusing on. Once I manage to get close enough to the VFE's heart to
drive a stake through it, I expect this issue to become quite easy to
fix as well.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
> Am 02.02.2017 um 03:26 schrieb Cousin Ricky:
> >
> > Guess what? The one thing those two scenes had in common that all my
> > other tests did not was Greek text.
> >
> > This appears to be the same charset utf8 bug that ThH uncovered. And
> > since LanuHum probably uses a lot of Cyrillic text, I'm guessing that
> > his is the same problem.
>
> [Clipka wrote...]
> Sounds totally plausible.
>
> If that is the case, then the next beta should fix it.
> [Clipka wrote...]
>> It would be interesting to know whether the latest tagged alpha
>> (v3.7.1-alpha.8927145) works better than the beta. Since we've made only
>> very few changes to the source code since then, that would give us a
>> clear hint where to search for things that might be going wrong.
>
> [Cousin Ricky wrote...]
> Alpha.8927145 crashes. Alpha.8917471 runs splendidly.
> [Clipka wrote...]
> That fits well with the theory that it's the "utf8" bug you're experiencing.
Sorry to be late with this, but...
I can confirm this charset utf8 crash bug, in two versions of POV-Ray (on
Windows 7 64-bit):
Alpha.8927145
and
3.7.1-beta 2
Does NOT crash when using the 'original' v3.7.0 version.
(I used the appropriate pvengine64 versions for each.)
The scene that I did the tests with is mentioned here (I simply commented-out
the scene's 'charset utf8' entry in global_settings)...
http://news.povray.org/povray.beta-test.binaries/thread/%3Cweb.5897b07b6a1a359883fb31c0%40news.povray.org%3E/
and
http://news.povray.org/povray.text.scene-files/thread/%3Cweb.4a7c8c12a399eaf3df22a6900%40news.povray.org%3E/?ttop=41306
4&toff=50
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
| |
|
|
On 2017-02-05 07:47 PM (-4), Kenneth wrote:
> Sorry to be late with this, but...
>
> I can confirm this charset utf8 crash bug, in two versions of POV-Ray (on
> Windows 7 64-bit):
>
> Alpha.8927145
> and
> 3.7.1-beta 2
>
> Does NOT crash when using the 'original' v3.7.0 version.
>
> (I used the appropriate pvengine64 versions for each.)
>
> The scene that I did the tests with is mentioned here (I simply commented-out
> the scene's 'charset utf8' entry in global_settings)...
>
>
http://news.povray.org/povray.beta-test.binaries/thread/%3Cweb.5897b07b6a1a359883fb31c0%40news.povray.org%3E/
>
> and
>
>
http://news.povray.org/povray.text.scene-files/thread/%3Cweb.4a7c8c12a399eaf3df22a6900%40news.povray.org%3E/?ttop=41306
> 4&toff=50
The latest master branch does not crash. I look forward to beta 3.
Post a reply to this message
|
|
| |
| |
|
|
|
|
| |
