From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8893 invoked by alias); 5 Apr 2011 08:58:20 -0000 Received: (qmail 8884 invoked by uid 22791); 5 Apr 2011 08:58:19 -0000 X-SWARE-Spam-Status: No, hits=-6.5 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_HI,SPF_HELO_PASS,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Tue, 05 Apr 2011 08:58:12 +0000 Received: from int-mx02.intmail.prod.int.phx2.redhat.com (int-mx02.intmail.prod.int.phx2.redhat.com [10.5.11.12]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id p358wC7N024839 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Tue, 5 Apr 2011 04:58:12 -0400 Received: from zebedee.pink (ovpn-113-109.phx2.redhat.com [10.3.113.109]) by int-mx02.intmail.prod.int.phx2.redhat.com (8.13.8/8.13.8) with ESMTP id p358wAQv015265; Tue, 5 Apr 2011 04:58:11 -0400 Message-ID: <4D9AD9A2.5000508@redhat.com> Date: Tue, 05 Apr 2011 08:58:00 -0000 From: Andrew Haley User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.15) Gecko/20110307 Fedora/3.1.9-0.39.b3pre.fc14 Thunderbird/3.1.9 MIME-Version: 1.0 To: java@gcc.gnu.org Subject: Re: GC leaks debugging References: <4D95909E.4060309@redhat.com> <4D959C24.8030408@redhat.com> <238A96A773B3934685A7269CC8A8D04272EFEFD5C3@GVW0436EXB.americas.hpqcorp.net> <4D997D8C.9060903@redhat.com> <4D9993D4.9040704@redhat.com> <238A96A773B3934685A7269CC8A8D04272EFF7D28D@GVW0436EXB.americas.hpqcorp.net> In-Reply-To: <238A96A773B3934685A7269CC8A8D04272EFF7D28D@GVW0436EXB.americas.hpqcorp.net> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact java-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-owner@gcc.gnu.org X-SW-Source: 2011-04/txt/msg00027.txt.bz2 On 05/04/11 05:41, Boehm, Hans wrote: > I'm still concerned about the amount of blacklisting here. Can you > track down some of those messages or calls to > GC_add_to_black_list_normal, and find out where those bogus > pointer-like bit patterns are coming from? > > Is there any way to get the reflection information (and exception > information? or was that fixed?) into read-only segments, so that > the collector can know not to scan them? It's not easy. That's already been done with indirect dispatch, but it doesn't work with the core library. The easiest way to get it working for all classes may be to get CNI working wthe indirect dispatch. Andrew.