This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: hints on debugging memory corruption...

From: Richard Henderson <rth at redhat dot com>
To: Dodji Seketeli <dodji at redhat dot com>
Cc: Joern Rennecke <joern dot rennecke at embecosm dot com>, Tom Tromey <tromey at redhat dot com>, Basile Starynkevitch <basile at starynkevitch dot net>, gcc at gcc dot gnu dot org
Date: Thu, 10 Feb 2011 10:02:39 -0800
Subject: Re: hints on debugging memory corruption...
References: <20110204154203.GA19472@ours.starynkevitch.net> <m3fws38y47.fsf@fleche.redhat.com> <20110204132857.v4qs3h8ktw8osscg-nzlynne@webmail.spamcop.net> <m3tygcarjs.fsf@redhat.com>

On 02/10/2011 06:32 AM, Dodji Seketeli wrote:
> For the sake of archiving these tricks how do you postpone garbage
> collection in practise?

Set --param ggc-min-heapsize to a very large value.


r~

Follow-Ups:
- Re: hints on debugging memory corruption...
  - From: Dodji Seketeli

References:
- hints on debugging memory corruption...
  - From: Basile Starynkevitch
- Re: hints on debugging memory corruption...
  - From: Tom Tromey
- Re: hints on debugging memory corruption...
  - From: Joern Rennecke
- Re: hints on debugging memory corruption...
  - From: Dodji Seketeli

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]