On Sep 15, 2013, at 2:15 PM, Vlad Bogolin wrote: > When closing the qt display manager sometimes a segfault occurs. I've seen > that this occurs after the close function is called and gdb says the > fallowing: > > Program received signal SIGSEGV, Segmentation fault. > __GI___pthread_mutex_lock (mutex=0x0) at pthread_mutex_lock.c:50 > 50 pthread_mutex_lock.c: No such file or directory. > > Any hints on what might cause this or where to look?
Can you reproduce the segfault in the debugger? You really need a stack trace or debugging information of some sort to go on. You can also try to compile BRL-CAD as single-threaded to see if the problem is specific to something Qt's doing or our parallelism. (cmake -DBRLCAD_ENABLE_SMP=NO) Cheers! Sean ------------------------------------------------------------------------------ LIMITED TIME SALE - Full Year of Microsoft Training For Just $49.99! 1,500+ hours of tutorials including VisualStudio 2012, Windows 8, SharePoint 2013, SQL 2012, MVC 4, more. BEST VALUE: New Multi-Library Power Pack includes Mobile, Cloud, Java, and UX Design. Lowest price ever! Ends 9/20/13. http://pubads.g.doubleclick.net/gampad/clk?id=58041151&iu=/4140/ostg.clktrk _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
