Main Site Documentation

CG status messages to output window... MAKE IT STOP!


#1

I am using a FEZ Domino with the latest SDK and Firmware.

I wrote a small program which read a file from the internal micro SD card. The file was about 700 bytes long and contained about 30 lines.

I used a StreamReader and the ReadLine() method to read a line at a time.

Everything worked fine… But there were several debug outputs from the GC mechanism.

I did not do a Debug.GC() call.

I could not find a way to stop the unsolicited CG status to the output window. I checked the project properties and did a search on the web.

Anyone have an idea how to stop the GC output? It make it hard to read the messages I am sending to the output window.

Thanks,
Mike


#2

You can’t stop them. This message is very useful to give you an idea of RAM usage levels. Plus it will tell you how good/bad your code is when ti comes to allocate/free objects. Ideally, you will make your application where it would never need to run the GC…in some cases you simply can’t.

See “thinking small” section in the book


#3

I get this too, although I don’t have too much of a problem with it. Would it be possible to enable/disable it in the FEZ side code?


#4

No it can’t be disabled. The output window is only used for debugging so does disabling those messages really help?


#5

I’d consider moving the “real” messages to a serial output if that’s important to your app, rather than just being a debug status message?


#6

Thanks for the reply to my question.

“The output window is only used for debugging so does disabling those messages really help”

I use the output window for debugging, so yes disabling those message would really help. My debugging messages are mixed in with the GC messages. That makes it really hard to read my messages.

But I will preface all of my messages with “***” so they will be easier to pick out of all the GC garbage.


#7

kinda ironic gc messages need to be collected and thorwn out.


#8

Those messages are very important and they do not effect performance.


#9

So what does the following do then…


            Debug.EnableGCMessages( false );


#10

The original post was made a few software releases ago. The method you showed was added at a later date. It does stop gc messages.


#11

worth closing the thread on a happy note then ;D


#12

Holy raise a thread from the dead batman.


#13

I see dead threads :o


#14

Enough heard from the deadheads.


#15

Bring out yer dead.
Here’s one.
That’ll be ninepence.
I’m not dead.
What?
Nothing. There’s your ninepence.
I’m not dead.
'Ere, he says he’s not dead.
Yes he is.
I’m not.
He isn’t.
Well, he will be soon, he’s very ill.
I’m getting better.
No you’re not, you’ll be stone dead in a moment.
Well, I can’t take him like that. It’s against regulations.


#16

OK… no more Monty Python…


#17

<3 monty python. Most silly americans dont get it.