Hi Don, I am curious, did you fix an issue, or was it using the MSYS2 build process that solved the problem, or was it the debug build that prevented the crash, or was it already fixed in the master? Thanks, Kit On Fri, Oct 30, 2015 at 10:12 PM, spinorkit <kit.adams@gmail.com> wrote: > This latest version runs fine. > I just had to check "Force Goldfeather" for the Preview to render > correctly. > > Many thanks, > Kit > > On Fri, Oct 30, 2015 at 4:07 PM, donbright [via OpenSCAD] <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=14250&i=0>> wrote: > >> >> Thanks for testing the msys2 build. Sorry about the error, it's my first >> time doing QT5 on Windows. >> >> Here is a new test MSYS2 build off the Master branch. I have tested it on >> Windows 7. >> >> http://files.openscad.org/snapshots/OpenSCAD-2015.10.29-msys2-x86-64.zip >> >> -- >> don bright >> [hidden email] <http:///user/SendEmail.jtp?type=node&node=14247&i=0> >> >> >> On Thu, Oct 29, 2015, at 05:01 PM, spinorkit wrote: >> >> Thanks for the debug build. >> It gets a bit further. >> Running openscad results in the error message in the attached screen shot >> before it terminates. >> >> The openscad --info command now gives: >> >> C:\Users\Kit\Downloads\OpenSCAD-2015.10.28-x86-64.msys2\openscad-2015.10.28>openscad >> --info >> debug pt 0 >> debug pt 1 >> debug pt 2 >> debug pt 3 >> debug pt 4 >> debug pt 5 >> debug pt 6 >> debug pt 7 >> debug pt 8 >> debug pt 9 >> debug pt 10 >> debug pt 11 >> debug pt 12 >> debug pt 13 >> debug pt 14 >> debug pt 15 >> debug pt 16 >> debug pt 17 >> debug pt 18 >> OpenSCAD Version: 2015.10.28 >> System information: Windows 8 (v6.2.0.0) 8 CPUs 15.88 GB RAM >> Compiler: GCC "5.2.0" 64bit >> Boost version: 1_57 >> Eigen version: 3.2.5 >> CGAL version, kernels: 4.6.1, Cartesian<Gmpq>, Extended_cartesian<Gmpq>, >> Epeck >> OpenCSG version: OpenCSG 1.4.0 >> Qt version: 5.5.0 >> QScintilla version: 2.9 >> MingW build: MingW64 >> GLib version: 2.44.1 >> Application Path: >> C:/Users/Kit/Downloads/OpenSCAD-2015.10.28-x86-64.msys2/openscad-2015.10.28 >> Documents Path: E:\Users\Kit\Documents >> Resource Path: >> C:/Users/Kit/Downloads/OpenSCAD-2015.10.28-x86-64.msys2/openscad-2015.10.28 >> User Library Path: E:/Users/Kit/Documents/OpenSCAD/libraries >> User Config Path: C:\Users\Kit\AppData\Local/OpenSCAD >> Backup Path: E:/Users/Kit/Documents/OpenSCAD/backups >> OPENSCADPATH: <not set> >> OpenSCAD library path: >> E:/Users/Kit/Documents/OpenSCAD/libraries >> >> C:/Users/Kit/Downloads/OpenSCAD-2015.10.28-x86-64.msys2/openscad-2015.10.28\libraries >> >> OPENSCAD_FONT_PATH: <not set> >> OpenSCAD font path: >> >> >> GLEW version: 1.12.0 >> OpenGL Version: 4.3.0 - Build 10.18.14.4264 >> GL Renderer: Intel(R) HD Graphics 4600 >> GL Vendor: Intel >> RGBA(8888), depth(24), stencil(8) >> GL_ARB_framebuffer_object: yes >> GL_EXT_framebuffer_object: yes >> GL_EXT_packed_depth_stencil: yes >> GL context creator: WGL >> PNG generator: lodepng >> OS info: Microsoft(TM) Windows(TM) 6 2 9200 0x23d0f4 amd64 >> Machine: 8664 >> >> >> C:\Users\Kit\Downloads\OpenSCAD-2015.10.28-x86-64.msys2\openscad-2015.10.28> >> >> >> >> On Fri, Oct 30, 2015 at 12:44 AM, donbright [via OpenSCAD] <[hidden >> email]> wrote: >> >> >> Hello >> >> A .zip package of an alternative build, using the MSYS2 Build System, has >> been uploaded here (note it is rather large, >50MB):: >> >> http://files.openscad.org/snapshots/OpenSCAD-2015.10.28-x86-64.msys2.zip >> >> Also this build has sprinkled openscad.cc with several debug print >> statements. Running this might help diagnose the problems... >> >> >> -- >> don bright >> [hidden email] <http:///user/SendEmail.jtp?type=node&node=14244&i=0> >> >> >> On Tue, Oct 27, 2015, at 04:46 AM, Kit Adams wrote: >> >> >> >> Actually, that dis-assembly and stack is for the 2015.03-1 build. The >> 2015.10.17 version crashes in similar code at address 0000000000F903F4 : >> mov rax,qword ptr [rdx] . >> >> >> >> On Tue, Oct 27, 2015 at 8:38 PM, spinorkit <[hidden email] >> <http:///user/SendEmail.jtp?type=node&node=14244&i=1>> wrote: >> >> >> >> >> and the stack: >> >openscad.exe!0000000000ff7a04()Unknown >> openscad.exe!0000000000ff867e()Unknown >> openscad.exe!0000000000ff9087()Unknown >> openscad.exe!0000000000fd3be3()Unknown >> openscad.exe!0000000000fd5ad9()Unknown >> openscad.exe!0000000000f9d6e5()Unknown >> openscad.exe!0000000000f9d9fd()Unknown >> openscad.exe!00000000004e8817()Unknown >> openscad.exe!00000000004edec1()Unknown >> openscad.exe!0000000000557eff()Unknown >> openscad.exe!00000000004013e8()Unknown >> openscad.exe!00000000004014eb()Unknown >> >> >> >> >> On Tue, Oct 27, 2015 at 8:36 PM, Kit Adams <[hidden email] >> <http:///user/SendEmail.jtp?type=node&node=14222&i=0>> wrote: >> >> In case it helps, the disassembly around the crash is: >> 0000000000FF79B5 call 0000000001001D10 >> 0000000000FF79BA mov r12,rax >> 0000000000FF79BD mov rbp,qword ptr [rsi+30h] >> 0000000000FF79C1 test rbp,rbp >> 0000000000FF79C4 je 0000000000FF7A60 >> 0000000000FF79CA cmp byte ptr [rsi+0D5h],0 >> 0000000000FF79D1 jne 0000000000FF7A60 >> 0000000000FF79D7 test r12,r12 >> 0000000000FF79DA jle 0000000000FF7B00 >> 0000000000FF79E0 mov rax,qword ptr [rsi+88h] >> 0000000000FF79E7 mov rdx,qword ptr [rsi+30h] >> 0000000000FF79EB lea rbx,[rsp+30h] >> 0000000000FF79F0 lea rcx,[rsi+38h] >> 0000000000FF79F4 mov r9d,r12d >> 0000000000FF79F7 lea r12,[rsi+88h] >> 0000000000FF79FE mov r8,rdi >> 0000000000FF7A01 mov ebp,dword ptr [rax+4] >> Null deference [rdx] here ->0000000000FF7A04 mov rax,qword ptr >> [rdx] >> 0000000000FF7A07 mov qword ptr [rsp+20h],rcx >> 0000000000FF7A0C mov rcx,rbx >> 0000000000FF7A0F call qword ptr [rax+18h] >> 0000000000FF7A12 mov rdx,rbx >> 0000000000FF7A15 mov rcx,r12 >> 0000000000FF7A18 call 00000000010440F0 >> 0000000000FF7A1D mov rcx,qword ptr [rsp+30h] >> 0000000000FF7A22 mov eax,dword ptr [rcx] >> 0000000000FF7A24 test eax,eax >> 0000000000FF7A26 jne 0000000000FF7AC3 >> 0000000000FF7A2C mov r8d,8 >> 0000000000FF7A32 mov edx,2 >> 0000000000FF7A37 call 00000000010BE1A0 >> 0000000000FF7A3C test r13b,r13b >> 0000000000FF7A3F jne 0000000000FF7B90 >> 0000000000FF7A45 mov eax,1 >> 0000000000FF7A4A add rsp,4048h >> 0000000000FF7A51 pop rbx >> 0000000000FF7A52 pop rsi >> 0000000000FF7A53 pop rdi >> 0000000000FF7A54 pop rbp >> 0000000000FF7A55 pop r12 >> 0000000000FF7A57 pop r13 >> 0000000000FF7A59 ret >> 0000000000FF7A5A nop word ptr [rax+rax] >> >> >> On Tue, Oct 27, 2015 at 8:26 PM, Kit Adams <[hidden email] >> <http:///user/SendEmail.jtp?type=node&node=14222&i=1>> wrote: >> >> On my Win8.0 machine, the 2015.10.17 build returns after a few seconds >> with no output. The 2014 build on the same machine returns: >> >> C:\Program Files\OpenSCAD>openscad.exe --info >> >> C:\Program Files\OpenSCAD>openscad --info >> OpenSCAD Version: 2014.03 >> Compiler, build date: GCC "4.8.1", Mar 9 2014 >> Boost version: 1_53 >> Eigen version: 3.1.3 >> CGAL version, kernels: 4.0.2, Cartesian<Gmpq>, Extended_cartesian<Gmpq>, >> Epeck >> OpenCSG version: OpenCSG 1.3.2 >> Qt version: 4.8.5 >> MingW build: MingW64 >> GLib version: 2.36.3 >> OPENSCADPATH: <not set> >> OpenSCAD library path: >> >> >> GLEW version: 1.9.0 >> OpenGL Version: 4.3.0 - Build 10.18.14.4264 >> GL Renderer: Intel(R) HD Graphics 4600 >> GL Vendor: Intel >> RGBA(8888), depth(24), stencil(8) >> GL_ARB_framebuffer_object: yes >> GL_EXT_framebuffer_object: yes >> GL_EXT_packed_depth_stencil: yes >> GL context creator: WGL >> PNG generator: lodepng >> OS info: Microsoft(TM) Windows(TM) 6 2 9200 0x1eaec74 amd64 >> Machine: 8664 >> >> C:\Program Files\OpenSCAD> >> >> Running openscad.exe --info crashes without output. The access violation >> is : >> Unhandled exception at 0x0000000000FF7A04 in openscad.exe: 0xC0000005: >> Access violation reading location 0x0000000000000000. >> >> >> Thanks, >> Kit >> >> On Tue, Oct 27, 2015 at 12:41 PM, donbright [via OpenSCAD] <[hidden >> email] <http:///user/SendEmail.jtp?type=node&node=14222&i=2>> wrote: >> >> >> My first question would be, can the user run "openscad --info" from the >> command line? >> >> ------------------------------ >> >> >> If you reply to this email, your message will be added to the discussion >> below: >> >> http://forum.openscad.org/Access-violation-on-starting-OpenSCAD-Win8-tp14201p14219.html >> To unsubscribe from Access violation on starting OpenSCAD (Win8), click >> here. >> NAML >> <http://forum.openscad.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> >> >> >> >> >> >> >> >> ------------------------------ >> View this message in context: Re: Access violation on starting OpenSCAD >> (Win8) >> <http://forum.openscad.org/Access-violation-on-starting-OpenSCAD-Win8-tp14201p14222.html> >> Sent from the OpenSCAD mailing list archive <http://forum.openscad.org/> >> at Nabble.com. >> >> _______________________________________________ >> OpenSCAD mailing list >> [hidden email] <http:///user/SendEmail.jtp?type=node&node=14244&i=2> >> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >> >> >> *_______________________________________________* >> OpenSCAD mailing list >> [hidden email] <http:///user/SendEmail.jtp?type=node&node=14244&i=3> >> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >> >> >> >> _______________________________________________ >> OpenSCAD mailing list >> [hidden email] <http:///user/SendEmail.jtp?type=node&node=14244&i=4> >> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >> >> >> ------------------------------ >> >> >> If you reply to this email, your message will be added to the discussion >> below: >> >> http://forum.openscad.org/Access-violation-on-starting-OpenSCAD-Win8-tp14201p14244.html >> To unsubscribe from Access violation on starting OpenSCAD (Win8), click >> here. >> NAML >> <http://forum.openscad.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> >> >> >> >> *OpenSCAD.png* (9K) Download Attachment >> <http://forum.openscad.org/attachment/14246/0/OpenSCAD.png> >> >> ------------------------------ >> View this message in context: Re: Access violation on starting OpenSCAD >> (Win8) >> <http://forum.openscad.org/Access-violation-on-starting-OpenSCAD-Win8-tp14201p14246.html> >> Sent from the OpenSCAD mailing list archive <http://forum.openscad.org/> >> at Nabble.com. >> *_______________________________________________* >> OpenSCAD mailing list >> [hidden email] <http:///user/SendEmail.jtp?type=node&node=14247&i=1> >> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >> >> >> >> _______________________________________________ >> OpenSCAD mailing list >> [hidden email] <http:///user/SendEmail.jtp?type=node&node=14247&i=2> >> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >> >> >> ------------------------------ >> If you reply to this email, your message will be added to the discussion >> below: >> >> http://forum.openscad.org/Access-violation-on-starting-OpenSCAD-Win8-tp14201p14247.html >> To unsubscribe from Access violation on starting OpenSCAD (Win8), click >> here. >> NAML >> <http://forum.openscad.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> >> > > > ------------------------------ > View this message in context: Re: Access violation on starting OpenSCAD > (Win8) > <http://forum.openscad.org/Access-violation-on-starting-OpenSCAD-Win8-tp14201p14250.html> > Sent from the OpenSCAD mailing list archive <http://forum.openscad.org/> > at Nabble.com. > > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org > >

            To unsubscribe from Access violation on starting OpenSCAD (Win8), click here.

Thanks for testing it out, that is good news. The MSYS2 build and link process is the only real difference between the versions. This is not a good permanent solution, for example the MSYS2 build required some nasty kludging of MSYS2 windeployqt which is why there are two identical 25 megabyte ICU .dll files with only a slightly different name in the download package. --   don bright   hmbright@fastmail.com On Fri, Oct 30, 2015, at 04:52 PM, Kit Adams wrote: > Hi Don, > I am curious, did you fix an issue, or was it using the MSYS2 build process that solved the problem, or was it the debug build that prevented the crash, or was it already fixed in the master? > Thanks, > Kit > > On Fri, Oct 30, 2015 at 10:12 PM, spinorkit <kit.adams@gmail.com> wrote: >> >> This latest version runs fine.  >> I just had to check "Force Goldfeather" for the Preview to render correctly. >> >> Many thanks, >> Kit >> >> >> On Fri, Oct 30, 2015 at 4:07 PM, donbright [via OpenSCAD] <[hidden email][1]> wrote: >>> >>> >>> Thanks for testing the msys2 build. Sorry about the error, it's my first time doing QT5 on Windows. >>> >>> Here is a new test MSYS2 build off the Master branch. I have tested it on Windows 7. >>> >>> http://files.openscad.org/snapshots/OpenSCAD-2015.10.29-msys2-x86-64.zip >>> >>> >>> -- >>>   don bright >>> [hidden email][2] >>> >>> >>> >>> >>> On Thu, Oct 29, 2015, at 05:01 PM, spinorkit wrote: >>> >>>> Thanks for the debug build. >>>> It gets a bit further. >>>> Running openscad results in the error message in the attached screen shot before it terminates. >>>> >>>> The openscad --info command now gives: >>>> >>>> C:\Users\Kit\Downloads\OpenSCAD-2015.10.28-x86-64.msys2\openscad-2015.10.28>openscad --info >>>> debug pt 0 >>>> debug pt 1 >>>> debug pt 2 >>>> debug pt 3 >>>> debug pt 4 >>>> debug pt 5 >>>> debug pt 6 >>>> debug pt 7 >>>> debug pt 8 >>>> debug pt 9 >>>> debug pt 10 >>>> debug pt 11 >>>> debug pt 12 >>>> debug pt 13 >>>> debug pt 14 >>>> debug pt 15 >>>> debug pt 16 >>>> debug pt 17 >>>> debug pt 18 >>>> OpenSCAD Version: 2015.10.28 >>>> System information: Windows 8 (v6.2.0.0) 8 CPUs 15.88 GB RAM >>>> Compiler: GCC "5.2.0" 64bit >>>> Boost version: 1_57 >>>> Eigen version: 3.2.5 >>>> CGAL version, kernels: 4.6.1, Cartesian<Gmpq>, Extended_cartesian<Gmpq>, Epeck >>>> OpenCSG version: OpenCSG 1.4.0 >>>> Qt version: 5.5.0 >>>> QScintilla version: 2.9 >>>> MingW build: MingW64 >>>> GLib version: 2.44.1 >>>> Application Path: C:/Users/Kit/Downloads/OpenSCAD-2015.10.28-x86-64.msys2/openscad-2015.10.28 >>>> Documents Path: E:\Users\Kit\Documents >>>> Resource Path: C:/Users/Kit/Downloads/OpenSCAD-2015.10.28-x86-64.msys2/openscad-2015.10.28 >>>> User Library Path: E:/Users/Kit/Documents/OpenSCAD/libraries >>>> User Config Path: C:\Users\Kit\AppData\Local/OpenSCAD >>>> Backup Path: E:/Users/Kit/Documents/OpenSCAD/backups >>>> OPENSCADPATH: <not set> >>>> OpenSCAD library path: >>>>   E:/Users/Kit/Documents/OpenSCAD/libraries >>>>   C:/Users/Kit/Downloads/OpenSCAD-2015.10.28-x86-64.msys2/openscad-2015.10.28\libraries >>>> >>>> OPENSCAD_FONT_PATH: <not set> >>>> OpenSCAD font path: >>>> >>>> >>>> GLEW version: 1.12.0 >>>> OpenGL Version: 4.3.0 - Build 10.18.14.4264 >>>> GL Renderer: Intel(R) HD Graphics 4600 >>>> GL Vendor: Intel >>>> RGBA(8888), depth(24), stencil(8) >>>> GL_ARB_framebuffer_object: yes >>>> GL_EXT_framebuffer_object: yes >>>> GL_EXT_packed_depth_stencil: yes >>>> GL context creator: WGL >>>> PNG generator: lodepng >>>> OS info: Microsoft(TM) Windows(TM) 6 2 9200 0x23d0f4 amd64 >>>> Machine: 8664 >>>> >>>> C:\Users\Kit\Downloads\OpenSCAD-2015.10.28-x86-64.msys2\openscad-2015.10.28> >>>> >>>> >>>> >>>> On Fri, Oct 30, 2015 at 12:44 AM, donbright [via OpenSCAD] <[hidden email]> wrote: >>>>> >>>>> Hello >>>>> >>>>> A .zip package of an alternative build, using the MSYS2 Build System, has been uploaded here (note it is rather large, >50MB):: >>>>> >>>>> http://files.openscad.org/snapshots/OpenSCAD-2015.10.28-x86-64.msys2.zip >>>>> >>>>> Also this build has sprinkled openscad.cc with several debug print statements. Running this might help diagnose the problems... >>>>> >>>>> >>>>> -- >>>>>   don bright >>>>> [hidden email][3] >>>>> >>>>> >>>>> On Tue, Oct 27, 2015, at 04:46 AM, Kit Adams wrote: >>>>> >>>>>> >>>>>> Actually, that dis-assembly and stack is for the 2015.03-1 build. The 2015.10.17 version crashes in similar code at address 0000000000F903F4 :  mov         rax,qword ptr [rdx] . >>>>>> >>>>>> >>>>>> >>>>>> On Tue, Oct 27, 2015 at 8:38 PM, spinorkit <[hidden email][4]> wrote: >>>>>> >>>>>>> >>>>>>> >>>>>>> and the stack: >>>>>>> >openscad.exe!0000000000ff7a04()Unknown >>>>>>> openscad.exe!0000000000ff867e()Unknown >>>>>>> openscad.exe!0000000000ff9087()Unknown >>>>>>> openscad.exe!0000000000fd3be3()Unknown >>>>>>> openscad.exe!0000000000fd5ad9()Unknown >>>>>>> openscad.exe!0000000000f9d6e5()Unknown >>>>>>> openscad.exe!0000000000f9d9fd()Unknown >>>>>>> openscad.exe!00000000004e8817()Unknown >>>>>>> openscad.exe!00000000004edec1()Unknown >>>>>>> openscad.exe!0000000000557eff()Unknown >>>>>>> openscad.exe!00000000004013e8()Unknown >>>>>>> openscad.exe!00000000004014eb()Unknown >>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> On Tue, Oct 27, 2015 at 8:36 PM, Kit Adams <[hidden email][5]> wrote: >>>>>>>> In case it helps, the disassembly around the crash is: >>>>>>>> 0000000000FF79B5  call        0000000001001D10   >>>>>>>> 0000000000FF79BA  mov         r12,rax   >>>>>>>> 0000000000FF79BD  mov         rbp,qword ptr [rsi+30h]   >>>>>>>> 0000000000FF79C1  test        rbp,rbp   >>>>>>>> 0000000000FF79C4  je          0000000000FF7A60   >>>>>>>> 0000000000FF79CA  cmp         byte ptr [rsi+0D5h],0   >>>>>>>> 0000000000FF79D1  jne         0000000000FF7A60   >>>>>>>> 0000000000FF79D7  test        r12,r12   >>>>>>>> 0000000000FF79DA  jle         0000000000FF7B00   >>>>>>>> 0000000000FF79E0  mov         rax,qword ptr [rsi+88h]   >>>>>>>> 0000000000FF79E7  mov         rdx,qword ptr [rsi+30h]   >>>>>>>> 0000000000FF79EB  lea         rbx,[rsp+30h]   >>>>>>>> 0000000000FF79F0  lea         rcx,[rsi+38h]   >>>>>>>> 0000000000FF79F4  mov         r9d,r12d   >>>>>>>> 0000000000FF79F7  lea         r12,[rsi+88h]   >>>>>>>> 0000000000FF79FE  mov         r8,rdi   >>>>>>>> 0000000000FF7A01  mov         ebp,dword ptr [rax+4]   >>>>>>>> Null deference [rdx] here ->0000000000FF7A04  mov         rax,qword ptr [rdx]   >>>>>>>> 0000000000FF7A07  mov         qword ptr [rsp+20h],rcx   >>>>>>>> 0000000000FF7A0C  mov         rcx,rbx   >>>>>>>> 0000000000FF7A0F  call        qword ptr [rax+18h]   >>>>>>>> 0000000000FF7A12  mov         rdx,rbx   >>>>>>>> 0000000000FF7A15  mov         rcx,r12   >>>>>>>> 0000000000FF7A18  call        00000000010440F0   >>>>>>>> 0000000000FF7A1D  mov         rcx,qword ptr [rsp+30h]   >>>>>>>> 0000000000FF7A22  mov         eax,dword ptr [rcx]   >>>>>>>> 0000000000FF7A24  test        eax,eax   >>>>>>>> 0000000000FF7A26  jne         0000000000FF7AC3   >>>>>>>> 0000000000FF7A2C  mov         r8d,8   >>>>>>>> 0000000000FF7A32  mov         edx,2   >>>>>>>> 0000000000FF7A37  call        00000000010BE1A0   >>>>>>>> 0000000000FF7A3C  test        r13b,r13b   >>>>>>>> 0000000000FF7A3F  jne         0000000000FF7B90   >>>>>>>> 0000000000FF7A45  mov         eax,1   >>>>>>>> 0000000000FF7A4A  add         rsp,4048h   >>>>>>>> 0000000000FF7A51  pop         rbx   >>>>>>>> 0000000000FF7A52  pop         rsi   >>>>>>>> 0000000000FF7A53  pop         rdi   >>>>>>>> 0000000000FF7A54  pop         rbp   >>>>>>>> 0000000000FF7A55  pop         r12   >>>>>>>> 0000000000FF7A57  pop         r13   >>>>>>>> 0000000000FF7A59  ret   >>>>>>>> 0000000000FF7A5A  nop         word ptr [rax+rax]   >>>>>>>> >>>>>>>> >>>>>>>> On Tue, Oct 27, 2015 at 8:26 PM, Kit Adams <[hidden email][6]> wrote: >>>>>>>>> On my Win8.0 machine, the 2015.10.17 build returns after a few seconds with no output. The 2014 build on the same machine returns: >>>>>>>>> >>>>>>>>> C:\Program Files\OpenSCAD>openscad.exe --info >>>>>>>>> >>>>>>>>> C:\Program Files\OpenSCAD>openscad --info >>>>>>>>> OpenSCAD Version: 2014.03 >>>>>>>>> Compiler, build date: GCC "4.8.1", Mar  9 2014 >>>>>>>>> Boost version: 1_53 >>>>>>>>> Eigen version: 3.1.3 >>>>>>>>> CGAL version, kernels: 4.0.2, Cartesian<Gmpq>, Extended_cartesian<Gmpq>, Epeck >>>>>>>>> OpenCSG version: OpenCSG 1.3.2 >>>>>>>>> Qt version: 4.8.5 >>>>>>>>> MingW build: MingW64 >>>>>>>>> GLib version: 2.36.3 >>>>>>>>> OPENSCADPATH: <not set> >>>>>>>>> OpenSCAD library path: >>>>>>>>> >>>>>>>>> >>>>>>>>> GLEW version: 1.9.0 >>>>>>>>> OpenGL Version: 4.3.0 - Build 10.18.14.4264 >>>>>>>>> GL Renderer: Intel(R) HD Graphics 4600 >>>>>>>>> GL Vendor: Intel >>>>>>>>> RGBA(8888), depth(24), stencil(8) >>>>>>>>> GL_ARB_framebuffer_object: yes >>>>>>>>> GL_EXT_framebuffer_object: yes >>>>>>>>> GL_EXT_packed_depth_stencil: yes >>>>>>>>> GL context creator: WGL >>>>>>>>> PNG generator: lodepng >>>>>>>>> OS info: Microsoft(TM) Windows(TM) 6 2 9200 0x1eaec74 amd64 >>>>>>>>> Machine: 8664 >>>>>>>>> >>>>>>>>> C:\Program Files\OpenSCAD> >>>>>>>>> >>>>>>>>> Running openscad.exe --info crashes without output. The access violation is : >>>>>>>>> Unhandled exception at 0x0000000000FF7A04 in openscad.exe: 0xC0000005: Access violation reading location 0x0000000000000000. >>>>>>>>> >>>>>>>>> >>>>>>>>> Thanks, >>>>>>>>> Kit >>>>>>>>> >>>>>>>>> On Tue, Oct 27, 2015 at 12:41 PM, donbright [via OpenSCAD] <[hidden email][7]> wrote: >>>>>>>>>> >>>>>>>>>> My first question would be, can the user run "openscad --info" from the command line? >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> If you reply to this email, your message will be added to the discussion below: >>>>>>>>>> http://forum.openscad.org/Access-violation-on-starting-OpenSCAD-Win8-tp14201p14219.html >>>>>>>>>> To unsubscribe from Access violation on starting OpenSCAD (Win8), click here. >>>>>>>>>> NAML[8] >>>>>>>>> >>>>>>>> >>>>>>> >>>>>>> >>>>>>> View this message in context: Re: Access violation on starting OpenSCAD (Win8)[9] >>>>>>> Sent from the OpenSCAD mailing list archive[10] at Nabble.com. >>>>>>> >>>>>>> _______________________________________________ >>>>>>> OpenSCAD mailing list >>>>>>> [hidden email][11] >>>>>>> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >>>>>>> >>>>>> _________________________________________________ >>>>>> OpenSCAD mailing list >>>>>> [hidden email][12] >>>>>> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >>>>> >>>>> >>>>> _______________________________________________ >>>>> >>>>> OpenSCAD mailing list >>>>> >>>>> [hidden email][13] >>>>> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >>>>> >>>>> >>>>> >>>>> >>>>> If you reply to this email, your message will be added to the discussion below: >>>>> http://forum.openscad.org/Access-violation-on-starting-OpenSCAD-Win8-tp14201p14244.html >>>>> To unsubscribe from Access violation on starting OpenSCAD (Win8), click here. >>>>> NAML[14] >>>> >>>> >>>> >>>> *OpenSCAD.png* (9K) Download Attachment[15] >>>> >>>> >>>> >>>> View this message in context: Re: Access violation on starting OpenSCAD (Win8)[16] >>>> Sent from the OpenSCAD mailing list archive[17] at Nabble.com. >>>> _________________________________________________ >>>> OpenSCAD mailing list >>>> [hidden email][18] >>>> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >>>> >>> >>> >>> >>> _______________________________________________ >>> >>> OpenSCAD mailing list >>> >>> [hidden email][19] >>> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >>> >>> >>> If you reply to this email, your message will be added to the discussion below: >>> >>> http://forum.openscad.org/Access-violation-on-starting-OpenSCAD-Win8-tp14201p14247.html >>> >>> To unsubscribe from Access violation on starting OpenSCAD (Win8), click here. >>> NAML[20] >>> >> >> >> View this message in context: Re: Access violation on starting OpenSCAD (Win8)[21] >> Sent from the OpenSCAD mailing list archive[22] at Nabble.com. >> >> _______________________________________________ >> OpenSCAD mailing list >> Discuss@lists.openscad.org >> http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org >> > _________________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org Links: 1. http:///user/SendEmail.jtp?type=node&node=14250&i=0 2. http:///user/SendEmail.jtp?type=node&node=14247&i=0 3. http:///user/SendEmail.jtp?type=node&node=14244&i=0 4. http:///user/SendEmail.jtp?type=node&node=14244&i=1 5. http:///user/SendEmail.jtp?type=node&node=14222&i=0 6. http:///user/SendEmail.jtp?type=node&node=14222&i=1 7. http:///user/SendEmail.jtp?type=node&node=14222&i=2 8. http://forum.openscad.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml 9. http://forum.openscad.org/Access-violation-on-starting-OpenSCAD-Win8-tp14201p14222.html 10. http://forum.openscad.org/ 11. http:///user/SendEmail.jtp?type=node&node=14244&i=2 12. http:///user/SendEmail.jtp?type=node&node=14244&i=3 13. http:///user/SendEmail.jtp?type=node&node=14244&i=4 14. http://forum.openscad.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml 15. http://forum.openscad.org/attachment/14246/0/OpenSCAD.png 16. http://forum.openscad.org/Access-violation-on-starting-OpenSCAD-Win8-tp14201p14246.html 17. http://forum.openscad.org/ 18. http:///user/SendEmail.jtp?type=node&node=14247&i=1 19. http:///user/SendEmail.jtp?type=node&node=14247&i=2 20. http://forum.openscad.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml 21. http://forum.openscad.org/Access-violation-on-starting-OpenSCAD-Win8-tp14201p14250.html 22. http://forum.openscad.org/

Hello There are some new test builds uploaded (listed below) using a very recent checkout of the MXE MingW cross build system. It would be extremely helpful if anyone with a Windows machine that crashed on OpenSCAD 2015 would be able to take a few minutes and test both a shared build and a static build, just enough to see if they still crash before bootup, and if not to see whether they will do a simple preview of a cube or whatever. http://files.openscad.org/snapshots/OpenSCAD-2015.11.11-MingW-x86-32-shared.zip http://files.openscad.org/snapshots/OpenSCAD-2015.11.11-MingW-x86-32-static.zip http://files.openscad.org/snapshots/OpenSCAD-2015.11.11-MingW-x86-64-shared.zip http://files.openscad.org/snapshots/OpenSCAD-2015.11.11-MingW-x86-64-static.zip Basically the theory being tested is whether or not the crash is caused by Static Linking vs Shared Linking... or whether it is just MXE / MingW in general that is causing the crash. Thanks!!!! -- don bright -- View this message in context: http://forum.openscad.org/Access-violation-on-starting-OpenSCAD-Win8-tp14201p14392.html Sent from the OpenSCAD mailing list archive at Nabble.com.

Hi, have tested OpenScad 2015-11-11 and it seems to work in my Win 10. I will continue to test. Regards Kent Ahlberg Den 151211 06:37 skrev Discuss on behalf of donbright <discuss-bounces@lists.openscad.org on behalf of hmbright@fastmail.com>: > >Hello > >There are some new test builds uploaded (listed below) using a very recent >checkout of the MXE MingW cross build system. > >It would be extremely helpful if anyone with a Windows machine that >crashed >on OpenSCAD 2015 would be able to take a few minutes and test both a >shared >build and a static build, just enough to see if they still crash before >bootup, and if not to see whether they will do a simple preview of a cube >or >whatever. > >http://files.openscad.org/snapshots/OpenSCAD-2015.11.11-MingW-x86-32-share >d.zip > >http://files.openscad.org/snapshots/OpenSCAD-2015.11.11-MingW-x86-32-stati >c.zip > >http://files.openscad.org/snapshots/OpenSCAD-2015.11.11-MingW-x86-64-share >d.zip > >http://files.openscad.org/snapshots/OpenSCAD-2015.11.11-MingW-x86-64-stati >c.zip > >Basically the theory being tested is whether or not the crash is caused by >Static Linking vs Shared Linking... or whether it is just MXE / MingW in >general that is causing the crash. > >Thanks!!!! > > >-- >don bright > > > > >-- >View this message in context: >http://forum.openscad.org/Access-violation-on-starting-OpenSCAD-Win8-tp142 >01p14392.html >Sent from the OpenSCAD mailing list archive at Nabble.com. > >_______________________________________________ >OpenSCAD mailing list >Discuss@lists.openscad.org >http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org

Hi Don, Both these static and shared builds run and display fine on my main Windows 8.0 machine where the 2015.03 build still crashes. Thanks, Kit On Thu, Nov 12, 2015 at 6:37 PM, donbright [via OpenSCAD] < ml-node+s1091067n14392h97@n5.nabble.com> wrote: > > Hello > > There are some new test builds uploaded (listed below) using a very recent > checkout of the MXE MingW cross build system. > > It would be extremely helpful if anyone with a Windows machine that > crashed on OpenSCAD 2015 would be able to take a few minutes and test both > a shared build and a static build, just enough to see if they still crash > before bootup, and if not to see whether they will do a simple preview of a > cube or whatever. > > > http://files.openscad.org/snapshots/OpenSCAD-2015.11.11-MingW-x86-32-shared.zip > > > http://files.openscad.org/snapshots/OpenSCAD-2015.11.11-MingW-x86-32-static.zip > > > http://files.openscad.org/snapshots/OpenSCAD-2015.11.11-MingW-x86-64-shared.zip > > > http://files.openscad.org/snapshots/OpenSCAD-2015.11.11-MingW-x86-64-static.zip > > Basically the theory being tested is whether or not the crash is caused by > Static Linking vs Shared Linking... or whether it is just MXE / MingW in > general that is causing the crash. > > Thanks!!!! > > > -- > don bright > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://forum.openscad.org/Access-violation-on-starting-OpenSCAD-Win8-tp14201p14392.html > To unsubscribe from Access violation on starting OpenSCAD (Win8), click > here > <http://forum.openscad.org/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=14201&code=a2l0LmFkYW1zQGdtYWlsLmNvbXwxNDIwMXwtMTM1NzI4MDMyMQ==> > . > NAML > <http://forum.openscad.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > -- View this message in context: http://forum.openscad.org/Access-violation-on-starting-OpenSCAD-Win8-tp14201p14402.html Sent from the OpenSCAD mailing list archive at Nabble.com.

Thanks to all testers..... hate to ask another favor but there is one last test... this build is off the 2015.03 branch http://files.openscad.org/snapshots/OpenSCAD-2015.11.13-x86-64.zip http://files.openscad.org/snapshots/OpenSCAD-2015.11.13-x86-32.zip The theory being tested here is to see if the build machine itself, including the version of gcc, libraries, linker, assembler, mxe, etc, is somehow causing the crash. (this build machine for the links above is a fresh debian linux 8 box with mxe updated a week or two ago). --   don bright   hmbright@fastmail.com On Thu, Nov 12, 2015, at 05:36 AM, spinorkit wrote: > Hi Don, > Both these static and shared builds run and display fine on my main Windows 8.0 machine where the 2015.03 build still crashes. > > Thanks, > Kit > > > On Thu, Nov 12, 2015 at 6:37 PM, donbright [via OpenSCAD] <[hidden email]> wrote: >> >> Hello >> >> >> There are some new test builds uploaded (listed below) using a very recent checkout of the MXE MingW cross build system. >> >> >> It would be extremely helpful if anyone with a Windows machine that crashed on OpenSCAD 2015 would be able to take a few minutes and test both a shared build and a static build, just enough to see if they still crash before bootup, and if not to see whether they will do a simple preview of a cube or whatever. >> >> >> http://files.openscad.org/snapshots/OpenSCAD-2015.11.11-MingW-x86-32-shared.zip >> >> http://files.openscad.org/snapshots/OpenSCAD-2015.11.11-MingW-x86-32-static.zip >> >> http://files.openscad.org/snapshots/OpenSCAD-2015.11.11-MingW-x86-64-shared.zip >> >> http://files.openscad.org/snapshots/OpenSCAD-2015.11.11-MingW-x86-64-static.zip >> >> Basically the theory being tested is whether or not the crash is caused by Static Linking vs Shared Linking... or whether it is just MXE / MingW in general that is causing the crash. >> >> >> Thanks!!!! >> >> >> >> -- >> >> don bright >> >> >> >> >> >> If you reply to this email, your message will be added to the discussion below: >> http://forum.openscad.org/Access-violation-on-starting-OpenSCAD-Win8-tp14201p14392.html >> To unsubscribe from Access violation on starting OpenSCAD (Win8), click here. >> NAML[1] > > > View this message in context: Re: Access violation on starting OpenSCAD (Win8)[2] > Sent from the OpenSCAD mailing list archive[3] at Nabble.com. > _________________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org Links: 1. http://forum.openscad.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml 2. http://forum.openscad.org/Access-violation-on-starting-OpenSCAD-Win8-tp14201p14402.html 3. http://forum.openscad.org/

Hi Don, Both these builds also run and display fine for me, unlike the original 2015.03. Thanks, Kit On Fri, Nov 13, 2015 at 8:18 PM, don bright <hmbright@fastmail.com> wrote: > Thanks to all testers..... > > hate to ask another favor but there is one last test... this build is off > the 2015.03 branch > > http://files.openscad.org/snapshots/OpenSCAD-2015.11.13-x86-64.zip > > http://files.openscad.org/snapshots/OpenSCAD-2015.11.13-x86-32.zip > > The theory being tested here is to see if the build machine itself, > including the version of gcc, libraries, linker, assembler, mxe, etc, is > somehow causing the crash. (this build machine for the links above is a > fresh debian linux 8 box with mxe updated a week or two ago). > > -- > don bright > hmbright@fastmail.com > > > On Thu, Nov 12, 2015, at 05:36 AM, spinorkit wrote: > > Hi Don, > Both these static and shared builds run and display fine on my main > Windows 8.0 machine where the 2015.03 build still crashes. > > Thanks, > Kit > > > On Thu, Nov 12, 2015 at 6:37 PM, donbright [via OpenSCAD] <[hidden email]> > wrote: > > > Hello > > There are some new test builds uploaded (listed below) using a very recent > checkout of the MXE MingW cross build system. > > It would be extremely helpful if anyone with a Windows machine that > crashed on OpenSCAD 2015 would be able to take a few minutes and test both > a shared build and a static build, just enough to see if they still crash > before bootup, and if not to see whether they will do a simple preview of a > cube or whatever. > > > http://files.openscad.org/snapshots/OpenSCAD-2015.11.11-MingW-x86-32-shared.zip > > > http://files.openscad.org/snapshots/OpenSCAD-2015.11.11-MingW-x86-32-static.zip > > > http://files.openscad.org/snapshots/OpenSCAD-2015.11.11-MingW-x86-64-shared.zip > > > http://files.openscad.org/snapshots/OpenSCAD-2015.11.11-MingW-x86-64-static.zip > > Basically the theory being tested is whether or not the crash is caused by > Static Linking vs Shared Linking... or whether it is just MXE / MingW in > general that is causing the crash. > > Thanks!!!! > > > -- > don bright > > > ------------------------------ > > > If you reply to this email, your message will be added to the discussion > below: > > http://forum.openscad.org/Access-violation-on-starting-OpenSCAD-Win8-tp14201p14392.html > To unsubscribe from Access violation on starting OpenSCAD (Win8), click > here. > NAML > <http://forum.openscad.org/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml> > > > > ------------------------------ > View this message in context: Re: Access violation on starting OpenSCAD > (Win8) > <http://forum.openscad.org/Access-violation-on-starting-OpenSCAD-Win8-tp14201p14402.html> > Sent from the OpenSCAD mailing list archive <http://forum.openscad.org/> > at Nabble.com. > *_______________________________________________* > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org > > > > _______________________________________________ > OpenSCAD mailing list > Discuss@lists.openscad.org > http://lists.openscad.org/mailman/listinfo/discuss_lists.openscad.org > >