Discarding "Thread has excited... " output

[=?ISO-8859-15?Q?Martin_P=F6pping?=]

Hello,

I am using threads in my program and getting hundreds of
"the thread has exited..." messages.

Is there a way to discard the output of these messages?


Regards,

Martin

 

[Kfir M]

I would advise against that. I think you should find out why it is doing it
first and fix it.

But anyhow to bypass it try:

try
{
// you're code
}
catch (Exception e)
{
// you can read the error code in e.Message
}

hope this helps.

 

[=?ISO-8859-15?Q?Martin_P=F6pping?=]

I would advise against that. I think you should find out why it is doing it
first and fix it.

Ahhh! So this is really an error?

I am also getting it, when I do not use threads sometimes.
Maybe because of the STAThread.

So why does this error occur normally?


Regards,
Martin

 

[Michael D. Ober]

This error occurs when you try to access a thread that has completed and
exited. It is normal to get it. However, if you get it when you aren't
expecting to get it, you need to debug your thread to find out why it is
exiting early.

Mike Ober.

 

[=?ISO-8859-15?Q?Martin_P=F6pping?=]

This error occurs when you try to access a thread that has completed and
exited. It is normal to get it. However, if you get it when you aren't
expecting to get it, you need to debug your thread to find out why it is
exiting early.

Ok an if it is normal to get it and i am expecting to get it...
Is the only way to discard it to use try/catch?

My current solution is to use a logging api and to write these errors to
a special log-file.


Regards,

Martin

 

[Willy Denoyette [MVP]]

Ok an if it is normal to get it and i am expecting to get it...
Is the only way to discard it to use try/catch?

My current solution is to use a logging api and to write these errors to a special
log-file.

You should only get these messages when running in the debugger, are you sure you get this
running release mode code?
Also, can you post the exact message you get?

Willy.