On Wed, Dec 29, 2010 at 9:30 PM, Monty Brandenberg <mo...@lindenlab.com> wrote: > On 12/29/2010 1:19 PM, Aleric Inglewood wrote: > >> yes, this is a "known" problem: the viewer sometimes locks the X display, >> if then you halt it in the debugger you're toast. > > I only have creaky old Debians at hand but wondered if those with > more modern distros with updated GTKs can work around it by > changing the 'gtk_debug_flags'. There's now a GTK_DEBUG_NOGRABS > flag (1 << 12, I think). Set that and play a bit. No guarantees, > you'll need very recent libs and I don't know at what point in > execution you'll need to set that flag. (The --gtk-debug and > --gdk-debug cmd options also drive this.) But there it is... >
Thank you two for you replies. I will try the gtk debug env later. Just to refine my original mail. I would understand if I hit a breakpoint and there is some graphics stuff going on. But I just *run* snowstorm under gdb by setting LL_WRAPPER. I have not one breakpoint set, neither do I interrupt the program at all. I just use the viewer and it will just lock up the whole X display sooner or later. When I use the viewer without gdb all is fine, no crashes, hang, all good. Cheers, Nicky P.S. I am not NickyP :) Not that I minded it Aleric, just to avoid confusion. or later. _______________________________________________ Policies and (un)subscribe information available here: http://wiki.secondlife.com/wiki/OpenSource-Dev Please read the policies before posting to keep unmoderated posting privileges
