[Bug 423] Iced tea openjdk1.6 and jdk1.7 crashes in remote x server (cygwin) environment

[bugzilla-daemon at icedtea.classpath.org]

http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=423





------- Comment #3 from balajiraman at ge.com  2010-02-05 21:10 -------
Created an attachment (id=295)
 --> (http://icedtea.classpath.org/bugzilla/attachment.cgi?id=295&action=view)
Crash dump with xrenderer on in remote x server environment

I tried to run valgrind on the app as i couldnt get any crash dump in normal
running scenario.
Here is the command below and the trace i got along with the crash dump.

valgrind --trace-children=yes --leak-check=yes --xml=yes
--xml-file=./xrender.log --smc-check=all
--db-command=/usr/lib64/jvm/java-1.6.0-openjdk-1.6.0/bin/jdb
/usr/lib64/jvm/java-1.6.0-openjdk-1.6.0/bin/java -Dsun.java2d.xrender=True
TestSwing
XRender pipeline enabled
vex amd64->IR: unhandled instruction bytes: 0x48 0xF 0xAE 0x4 0x24 0x49
==20939== valgrind: Unrecognised instruction at address 0x773dc46.
==20939== Your program just tried to execute an instruction that Valgrind
==20939== did not recognise.  There are two possible reasons for this.
==20939== 1. Your program has a bug and erroneously jumped to a non-code
==20939==    location.  If you are running Memcheck and you just saw a
==20939==    warning about a bad jump, it's probably your program's fault.
==20939== 2. The instruction is legitimate but Valgrind doesn't handle it,
==20939==    i.e. it's Valgrind's fault.  If you think this is the case or
==20939==    you are not sure, please let us know and we'll try to fix it.
==20939== Either way, Valgrind will now raise a SIGILL signal which will
==20939== probably kill your program.


-- 
Configure bugmail: http://icedtea.classpath.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.