Hi, > I've stumbled upon a very annoying segmentation fault. It is triggered by > performing an Alt-TAB operation while gitk is running. If gitk is not > running, everything runs fine.
FWIW, I don't see that behaviour. It may have to do with 32 vs. 64 bit differences. > Here's the backtrace from GDB: > #0 memcpy () at ../sysdeps/x86_64/memcpy.S:267 > #1 0x000000000040f692 in imageToTexture (screen=0xe5cf40, > texture=0x1383c20, image=0x1383c70 "\377\377\377\377\003", > width=4290772992, height=4290772992, format=32993, type=5121) at > texture.c:114 > #2 0x000000000040f986 in imageBufferToTexture (screen=0xe5cf40, > texture=0x1383c20, image=0x1383c70 "\377\377\377\377\003", > width=4290772992, height=4290772992) at texture.c:180 > #3 0x000000000040fad9 in iconToTexture (screen=0xe5cf40, icon=0x1383c20) > at texture.c:229 Something must be very, very wrong with that icon. A width and height of 4 billion pixels is obviously wrong ;-) What's the output of 'xprop' and 'xprop 32c _NET_WM_ICON' for the gitk window? Does initiating scale at the same time work (and show the icons)? Regards, Danny _______________________________________________ Dev mailing list Dev@lists.compiz-fusion.org http://lists.compiz-fusion.org/mailman/listinfo/dev
