public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "green at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/21115] false boolean argument passed from pre-compiled to interpreted method is true
Date: Wed, 20 Apr 2005 00:50:00 -0000	[thread overview]
Message-ID: <20050420005053.1369.qmail@sourceware.org> (raw)
In-Reply-To: <20050419223032.21115.mark@gcc.gnu.org>


------- 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


  parent reply	other threads:[~2005-04-20  0:50 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-19 22:30 [Bug java/21115] New: " mark at gcc dot gnu dot org
2005-04-19 22:55 ` [Bug java/21115] " daney at gcc dot gnu dot org
2005-04-19 23:35 ` [Bug libgcj/21115] " pinskia at gcc dot gnu dot org
2005-04-20  0:50 ` green at redhat dot com [this message]
2005-04-20  0:57 ` pinskia at gcc dot gnu dot org
2005-04-20  1:37 ` tromey at gcc dot gnu dot org
2005-04-20  5:06 ` green at redhat dot com
2005-04-20 14:07 ` pinskia at gcc dot gnu dot org
2005-04-20 14:30 ` mark at gcc dot gnu dot org
2005-04-20 14:38 ` aph at gcc dot gnu dot org
2005-04-21 13:38 ` aph at gcc dot gnu dot org
2005-04-21 15:02 ` [Bug java/21115] " aph at gcc dot gnu dot org
2005-04-21 16:04 ` [Bug libgcj/21115] " mark at gcc dot gnu dot org
2005-04-21 16:06 ` [Bug java/21115] " pinskia at gcc dot gnu dot org
2005-04-21 16:23 ` cvs-commit at gcc dot gnu dot org
2005-04-28 16:35 ` cvs-commit at gcc dot gnu dot org
2005-04-29 18:43 ` cvs-commit at gcc dot gnu dot org
2005-04-29 18:44 ` cvs-commit at gcc dot gnu dot org
2005-04-29 19:24 ` pinskia at gcc dot gnu dot org

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20050420005053.1369.qmail@sourceware.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).