gc problem?

Tue Oct 23 18:44:00 GMT 2001

In theory, it should already go away if you set the environment variable
GC_NO_BLACKLIST_WARNING. All GC warnings are printed by calling
*GC_current_warn_proc, which could do filtering. I'm not claiming that
either of these is necessarily the perfect solution. 
(The collector now recognizes a bunch of GC_ environment variables. The
ones I find most useful are GC_PRINT_STATS, GC_INITIAL_HEAP_SIZE, and
GC_LOOP_ON_ABORT. See boehm-gc/doc/README.environment. This doesn't work
in the 3.0 tree.)
Hans
> -----Original Message-----
> From: Anthony Green [ mailto:green@redhat.com ]
> Sent: Tuesday, October 23, 2001 6:41 PM
> To: tromey@redhat.com; Boehm, Hans
> Cc: Java@Gcc. Gnu. Org
> Subject: Re: gc problem?
>>> Tom wrote:
> > Not yet. It is on my to-do list, but it is about 20 items down and
> > things get added to the top every day. So I'd say it is a low
> > probability fix :-(
>> Shouldn't we disable the warning instead? Or, at least, make 
> it a runtime
> option?
>> AG
>>