------- Additional Comments From green at redhat dot com 2005-04-20 00:50
-------
valgrind indicates that this uninitialized memory read is cause the bad
behaviour:
green ==12019== Conditional jump or move depends on uninitialised value(s)
green ==12019== at 0x1BEEB99C: _Jv_InterpMethod::run(void*, ffi_raw*)
(interpret.cc:2113)
green ==12019== by 0x1BEEFF5A: _Jv_InterpMethod::run_normal(ffi_cif*, void*,
ffi_raw*, void*) (interpret.cc:277)
green ==12019== by 0x1C2F51B9: ffi_closure_raw_SYSV (ffi.c:416)
green ==12019== by 0x80489EE: Test::main(JArray<java::lang::String*>*) (in
/home/green/pr21115/a.out)
interpet.cc:2113 is the ifeq opcode.
So it seems that either libffi is buggy, or we're using it incorrectly.
--
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|unassigned at gcc dot gnu |green at redhat dot com
|dot org |
Status|UNCONFIRMED |ASSIGNED
Ever Confirmed| |1
Last reconfirmed|0000-00-00 00:00:00 |2005-04-20 00:50:52
date| |
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21115
