Turn off garbage collector stats

Is there a way to turn off the garbage collector stats on the debug output?

I’m referring to this stuff…

[quote]GC: 2msec 14712 bytes used, 49668 bytes available
Type 0F (STRING ): 84 bytes
Type 11 (CLASS ): 888 bytes
Type 12 (VALUETYPE ): 36 bytes
Type 13 (SZARRAY ): 2460 bytes
Type 15 (FREEBLOCK ): 49668 bytes
Type 16 (CACHEDBLOCK ): 228 bytes
Type 17 (ASSEMBLY ): 7620 bytes
Type 18 (WEAKCLASS ): 48 bytes
Type 19 (REFLECTION ): 24 bytes
Type 1B (DELEGATE_HEAD ): 180 bytes
Type 1D (OBJECT_TO_EVENT ): 96 bytes
Type 1E (BINARY_BLOB_HEAD ): 228 bytes
Type 1F (THREAD ): 1152 bytes
Type 20 (SUBTHREAD ): 144 bytes
Type 21 (STACK_FRAME ): 612 bytes
Type 22 (TIMER_HEAD ): 72 bytes
Type 27 (FINALIZER_HEAD ): 72 bytes
Type 31 (IO_PORT ): 108 bytes
Type 34 (APPDOMAIN_HEAD ): 72 bytes
Type 36 (APPDOMAIN_ASSEMBLY ): 588 bytes[/quote]

Debug.enablegcmessages(false);

Or something to that effect.

EDIT: It’s in the debug class…

Thanks, Chris - that’s it:

[quote]
Debug.EnableGCMessages(false);[/quote]

I’ve never hit this one before. I went back and checked - all my other MF devices have this defaulted to false. It would be nice if you could set this in the build options.

Yep, I think it’s custom to GHI’s version of NETMF.

It is actually the other way around, we have the default but some others are hacked to remove these.

Why would anyone put effort into removing a feature? It’s not like the Deug.Print’s really effect anything…

Chris:

It can difficult to follow debugging output when the GC stuff is mixed in…

Yeah, I know, that’s my point. Why would the board dev go to the trouble of disabling the msg option?

Chris:

Ah! I now see your point.

When I started to use MF my first thought was to turn off the messages. I guess other MF providers had a similar thought.