From: Rampf on
We have coded a .NET CF application with several threads.

Now after exiting, at least one thread is not correctly closing, so it
hangs.

How can I see which one it is?

Thanks

From: Chris Tacke, eMVP on
The CF 3.5 profiler may well help you out on this. The other option would
be to simply dump out your thread ID when you start up a thread (debug
message is fine) and then use remote process viewer to view the process list
to see what threads are or are not running.


--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com

"Rampf" <rampf(a)rampf.com> wrote in message
news:O1fAD5inIHA.3940(a)TK2MSFTNGP05.phx.gbl...
> We have coded a .NET CF application with several threads.
>
> Now after exiting, at least one thread is not correctly closing, so it
> hangs.
>
> How can I see which one it is?
>
> Thanks


From: Christopher Fairbairn on
Hi,

"Rampf" <rampf(a)rampf.com> wrote in message
news:O1fAD5inIHA.3940(a)TK2MSFTNGP05.phx.gbl...
> Now after exiting, at least one thread is not correctly closing, so it
> hangs.
>
> How can I see which one it is?

If you are using Visual Studio as a debugger, one approach would be to place
a breakpoint at the end of your Main method (just before it returns and the
application exits).

When this break point is reached you should be able to use the Threads debug
window (accessible via the Debug main menu) to see what threads are still
active within your process. By looking at their callstacks etc you might get
a clue with respect to which tread has not shutdown properly.

Hope this helps,
Christopher Fairbairn