Glauber, I checked out and built from the git master with no avail. I built fluxus with and without flags, but I have the same problems as before. Thanks for your help.
-Stephen Halter P.S. The rev: 173 drivers are the latest binary drivers compatible with the nvidia geforce 5200 fx cards. On Sat, Apr 25, 2009 at 7:13 PM, Glauber Alex Dias Prado <[email protected]> wrote: > Stephen Halter <[email protected]> writes: > >> Hey guys, >> >> I have spent quite a while to get fluxus to work correctly with no >> luck. I seem to be having the exact same problem Glauber Alex Dias >> Prado had in March ( found here: >> http://lists.pawfal.org/pipermail/fluxus-pawfal.org/2009-March/002151.html >> ). I'm running Kubuntu 9.04 Jaunty 64-bit using the recently uploaded >> fluxus-0.16rc1. I'm getting a segfault with a gdb stack trace is very >> similar to Prado's every time I render something like (build-cube), >> (draw-cube), (build-sphere), etc. However, like Prado, the blobbies >> example works just fine. >> >> I realize this error propagates in libGLcore.so.1 which is the domain >> of the driver (I'm using the nvidia binary driver rev: 173.14.16. I've >> also attempted to get fluxus to work with the rev: 96 driver), but I >> have tried several drivers with the exact same result. (I have an >> nvidia geforce fx 5200 card which is why I haven't tried the rev: 180 >> drivers). Every other 3d application I've run works without a glitch, >> and, as mentioned above, the blobbies example works, so I would think >> there is an issue beyond the driver here. Here is the stack trace: >> >> SIGSEGV fault on (nil) >> >> Program received signal SIGABRT, Aborted. >> [Switching to Thread 0x7f8992026790 (LWP 4887)] >> 0x00007f898ea51fb5 in raise () from /lib/libc.so.6 >> (gdb) bt >> #0 0x00007f898ea51fb5 in raise () from /lib/libc.so.6 >> #1 0x00007f898ea53bc3 in abort () from /lib/libc.so.6 >> #2 0x00007f899193a481 in fault_handler (sn=<value optimized out>, >> si=0x7fff9a21f030, ctx=<value optimized out>) >> at ./sighand.c:49 >> #3 <signal handler called> >> #4 0x000000004097fa0e in ?? () >> #5 0x0000000040dd2000 in ?? () >> #6 0x00007f898668d18c in ?? () >> #7 0x000000000000000d in ?? () >> #8 0x000000000000000b in ?? () >> #9 0x00007f898d6db90c in ?? () from /usr/lib/libGLcore.so.1 >> #10 0x00007f898a79264d in Fluxus::PolyPrimitive::Render >> (this=0x1e42740) at libfluxus/src/PolyPrimitive.cpp:176 >> #11 0x00007f898a7b1683 in Fluxus::SceneGraph::RenderWalk >> (this=0x1d567b8, node=0x1e43000, depth=0, cameracode=1, >> shadowgen=0x1d56898, rendermode=Fluxus::SceneGraph::RENDER) at >> libfluxus/src/SceneGraph.cpp:94 >> #12 0x00007f898a7b170a in Fluxus::SceneGraph::Render (this=0x1d567b8, >> shadowgen=0x1d56898, camera=<value optimized out>, >> rendermode=Fluxus::SceneGraph::RENDER) at >> libfluxus/src/SceneGraph.cpp:43 >> #13 0x00007f898a7afdd3 in Fluxus::Renderer::Render (this=0x1d56710) at >> libfluxus/src/Renderer.cpp:138 >> #14 0x00007f898a74ff63 in fluxus_render (argc=<value optimized out>, >> argv=0x0) >> at modules/fluxus-engine/src/FluxusEngine.cpp:149 >> #15 0x00007f89888271d7 in ?? () >> #16 0x00007f898b6f8008 in ?? () >> #17 0x00007f8986453aea in ?? () >> #18 0x00007fff00000000 in ?? () >> #19 0x0000000000000005 in ?? () >> #20 0x0000000000000001 in ?? () >> #21 0x00007f8991be1d58 in scheme_multiple_values () from >> /usr/local/lib/libmzscheme3m-4.1.5.so >> #22 0x00007f8991bb04a0 in disappeared_binding_symbol () from >> /usr/local/lib/libmzscheme3m-4.1.5.so >> #23 0x0000000000000000 in ?? () >> >> Thank you for any of your help, >> Stephen Halter >> >> P.S. I've spent the last two days combing through your mailing list on >> and off with no avail. I did try using fluxus-0.15, but it was a pain >> in the ass to compile with GCC 4.3.3. I fixed all the headers so it >> would compile, but it segfaulted immediately. I then saw in you >> mailing list someone else with the newer GCC had more luck with 0.16 >> from the repo, and by the time I read it it was already available for >> download from the website. I'm confident that 0.16 is the more likely >> of the two versions to work. Every thing other than the rendering bug >> seems fine, but I guess I find out for sure if and when I get this bug >> worked out. >> >> Thanks again. > Try git master, gabor and dave fixed this, i didnt tried without GLSL=0 > and MULTITEXTURE=0 though,and on latest GLSL flag isnt needed anymore. > Also update your drivers to latest, this is what i did and its > working! > > cheers, > glauber. >
