Yep. Its just not enough info to be *sure* .. Someone should file a specific bug on this so it can be investigated. Dmitri?
-phil. Alan Coopersmith wrote: > Unless libmawt.so is passing an invalid pointer to libXext or > some unrelated part of code has corrupted memory. > > The stack trace is too limited too tell. > > -Alan Coopersmith- alan.coopersmith at sun.com > Sun Microsystems, Inc. - X Window System Engineering > > Dmitri Trembovetski wrote: >> >> Well, if it's dying in libXext then it is an X11 bug. >> >> Thanks, >> Dmitri >> >> Phil Race wrote: >>>> C [libX11.so.4+0x24831] _XReply+0x3c1 >>>> C [libXext.so.0+0x7f6b] XShmGetImage+0xef >>>> C [libmawt.so+0x12367] >>>> C [libmawt.so+0x11c5a] >>> >>> There were a number of updates to Xorg etc recently and they may be >>> part of the puzzle. >>> So this could be a bug in libX11 ..or perhaps in the JDK's XAWT >>> toolkit .. >>> or perhaps something else its hard to say. >>> JDk 6 defaults to using XAWT whereas 1.5 defaulted to MAWT (uses motif) >>> Maybe that could be a workaround .. but I am not sure since this is >>> not really involving >>> XAWT at this point where it crashes. >>> >>> http://java.sun.com/javase/6/docs/technotes/guides/awt/1.5/xawt.html >>> >>> -Phil. >>> >>> >>> This message posted from opensolaris.org >>> _______________________________________________ >>> desktop-discuss mailing list >>> desktop-discuss at opensolaris.org >> _______________________________________________ >> desktop-discuss mailing list >> desktop-discuss at opensolaris.org > >
