From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23598 invoked by alias); 16 Oct 2008 17:58:00 -0000 Received: (qmail 23580 invoked by uid 48); 16 Oct 2008 17:58:00 -0000 Date: Thu, 16 Oct 2008 17:58:00 -0000 Subject: [Bug libgcj/37856] New: Abort with: Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS X-Bugzilla-Reason: CC Message-ID: Reply-To: gcc-bugzilla@gcc.gnu.org To: java-prs@gcc.gnu.org From: "doko at ubuntu dot com" Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: java-prs-owner@gcc.gnu.org X-SW-Source: 2008-q4/txt/msg00001.txt.bz2 see PR37855 for the use case (building icedtea --with-alt-jar=gjar $ /usr/bin/gjar c0mf /scratch/packages/openjdk/d/icedtest/openjdk/control/build/linux-i586/tmp/manifest.tmp /scratch/packages/openjdk/d/icedtest/openjdk/control/build/linux-i586/tmp/rt-orig.jar @/scratch/packages/openjdk/d/icedtest/openjdk/control/build/linux-i586/tmp/jarfilelists/rt_jar_list_args -J-client -J-Xmx896m -J-Xms128m -J-XX:PermSize=32m -J-XX:MaxPermSize=160m Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS Aborted In the past there was some dicussion about setting LARGE_CONFIG, see http://gcc.gnu.org/ml/java-patches/2005-q4/msg00149.html and in the followup: "For the branch, I wanted to solve the problem while making the least intrusive change possible. On HEAD, it sounds like LARGE_CONFIG is the way to go. I will test a patch shortly and reverse the MAX_ROOT_SETS change there." -- Summary: Abort with: Too many heap sections: Increase MAXHINCR or MAX_HEAP_SECTS Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgcj AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: doko at ubuntu dot com http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37856