public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "kostikbel at ukr dot net" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/24120] New: jc1 incorrectly uses libiberty hashes
Date: Thu, 29 Sep 2005 12:38:00 -0000	[thread overview]
Message-ID: <20050929123754.24120.kostikbel@ukr.net> (raw)

(At least ) in gcc/java/jfc-io.c,
the memoized_dirlists hash is created by the call
 htab_create (37, htab_hash_string <-- NOTE THIS, memoized_dirlist_lookup_eq, NULL);
Actually, htab contains the structures (memoized_dirlist_entry), not the strings.

All went ok until hashtab.c decides it need to expand hash. Then,
libiberty/hashtab.c, htab_expand function tries to calculate hashes of hash entries
itself, calling htab_hash_string on elements of hash, that are not the strings,
but the structures.

When this happens, under right conditions jc1 crashes with SIGSEGV.
I found this on FreeBSD 6-CURRENT with debug malloc that fills uninitialized
storage with 0xd0. The problem is platform independent.

It seems that such code is present at least in 3.4.4, 4.0.2 and HEAD.

-- 
           Summary: jc1 incorrectly uses libiberty hashes
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: java
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: kostikbel at ukr dot net
                CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu
                    dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24120


             reply	other threads:[~2005-09-29 12:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-29 12:38 kostikbel at ukr dot net [this message]
2005-09-29 17:18 ` [Bug java/24120] " tromey at gcc dot gnu dot org
2005-09-30  0:34 ` cvs-commit at gcc dot gnu dot org
2005-09-30  0:36 ` cvs-commit at gcc dot gnu dot org
2005-09-30  0:37 ` tromey at gcc dot gnu dot org
2005-09-30  8:25 ` kostikbel at ukr dot net

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=20050929123754.24120.kostikbel@ukr.net \
    --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).