C#/.NET Threading

[MarkCuering]

---

Anyone care to talk about this? How do you find it?

[eax]

Just easy to implement and hard to debug/trace.

[MarkCuering]

what side of .NET Threading you have touch so far?

[bluedes]

what side of .NET Threading you have touch so far?

.Net threads are sloooooowwwwwww...

but if you're just limited to windows and .Net, guess you have no other choice.. unless u go java on windows.. although i love C# language, personally, i haven't tried threads on it yet..

but there's pthreads and gcc.. you can debug and trace separate threads.. gdb has features for it.. pero poor man's debugger ni ha.. but u can use eclipse if u want fancy ide..

[dodie]

tracelog or log file is the answer. Debug is the second answer.

[MarkCuering]

.Net threads are sloooooowwwwwww...

but if you're just limited to windows and .Net, guess you have no other choice.. unless u go java on windows.. although i love C# language, personally, i haven't tried threads on it yet..

but there's pthreads and gcc.. you can debug and trace separate threads.. gdb has features for it.. pero poor man's debugger ni ha.. but u can use eclipse if u want fancy ide..

How do you know it works slow when you still haven't tried it yet? There are alot of issues that slows down a thread.

[MarkCuering]

tracelog or log file is the answer. Debug is the second answer.

Sorry, but for me you cannot examine threads on tracelog or log file, I don't know what you are trying to tell me. Debugging as a second answer is also not clear in my point of view Threads are nearly impossible to debug, even in unmanaged C++, then how much more it is in C#.NET,

.NET threads is obviously different from OS Threads, I'm quite confuse, normally in C++ we wait the handle, but in C# you can get by its id., when you run the debugger, the debugger itself manages its own thread, and your debugger doesn't have controls to the thread you created in your program.

Its almost 2weeks I studied this, there are still issues that I don't get. Aside from that, .NET came along with different versions, unfortunately, they didn't remove the previous version of .NET threading, it is still on the namespaces scramble altogether!.

there are alot of ways to do threading in .NET, different ways to lock, there is ThreadStart, parameterized, pinvoke etc... anyone who came along from unmanged C++ and new at .NET will really get confused on this.

I can't use my tools for the meantime, but they said they will be supporting early next year, that's why I keep working on this

[dodie]

so it means you haven't tried tracelogging. hahahahahahahahahaha hahahahahahahahahahahahahah You are limiting yourself on debugging alone.
Debug feature alone is useless in some scenarios.

[MarkCuering]

so it means you haven't tried tracelogging. hahahahaha. You are limiting yourself on debugging alone.

I'm talking about threads you cannot trace nor log a thread, only the data handle or the memory shared by multiple threads, there's a routine for tracing and logging for modern compilers eg. profiler and tracer in .NET, JAVA, C++, Python.

here's the link of what bluedes talking about https://computing.llnl.gov/tutorials/pthreads/

but then again, my concern is C#.NET Threading... which one is commonly use? feedbacks? I tried to search the threading history of .NET since its first release, they didn't document that. instead they introduce only in readme files.

[dodie]

you cannot trace nor log a thread

hahahahahahahahaha, so innocent. Are you a programmer? What the..........

Of course, debugging can't do that. Tracelogging does.