C#/.NET Threading

[dodie]

---

I think you're the one who is misleading the new learners. Telling things they DON'T KNOW and making false information.

Telling much abbreviations, and didn't even know the real stuff behind it.

That's why I just tell ideas, and not telling much details.

[MarkCuering]

The Profiler I'm talking about is like this: Write Profilers With Ease Using High-Level Wrapper Classes

that's the best way to do some tracing and logging I've seen so far. they introduced some examples there that includes threading. but I'm still not convinced, I don't know either how far this is now at recent released.

As you can see, CLR developers are good in C++, and they aren't in C# standpoint. What they did is only wrap it on C# style, they only make it more easily to use, but not on the performance. just like what happened in WinXP to Windows Vista. The most difficult part is, Threads are created on .NET framework, not directly on the OS Platform. so if you want to do some tracing, logging, debugging, you got to work it on CLR.

like what I said, I got tool for this, but it will be on next year before they will release it.

[dodie]

everything is pointless if you don't know how to tracelog. We are talking threading here... hello!!!!!

[MarkCuering]

yup Threading in .NET, and that includes performance tuning tracing and logging is different, but if you can show me what you mean by that please do and how does it relate to .NET Threading, I will be glad to have your answers.

The site I mentioned introduces a well-rounded of profiling a thread, that you can do some tracing and logging on the datas handled by that particular thread. Don't forget to read their conclusion.
you are not actually logging a thread but data being pass and handle on that specific thread, via call back interface, let says "thread 1: hey, i take this memory, I return this to you", "thread 2: im handling this argument, would you log this?". BUT NOTE: the communication is only at the CLR level, this thread is also handle at OS LEVEL where real performance counts.. so how would you trace and log that again?

But I was not still convinced because they introduced another API... we are fully loaded with API, whats the point of making a framework when we still need to work on API just to hide some disadvantages on their Threading. (I still don't know if this is valid though in recent .NET, site concludes that it is on .NET2.0)

Anyway, it seems that you are dying of trying to kill me with your flame. your the dumbest person I ever talk on this forum. I can consider other people's answers except yours, which is totally DUMB!

[dodie]

your the dumbest person I ever talk on this forum. I can consider other people's answers except yours, which is totally DUMB!

I'm not just DUMB. I'm the weirdest person you'll ever know. You talk too much which is pointless. You claim that you don't tracelog, which is totally dumb.
You don't tracelog the thread? WTF!!!! go back to school!

Yes I do flame or sarcasm, but I don't claim stuff.

[MarkCuering]

I'm not just DUMB. I'm the weirdest person you'll ever know. You talk too much which is pointless. You claim that you don't tracelog, which is totally dumb.
You don't tracelog the thread? WTF!!!! go back to school!

from my previous post:

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,

I'm talking about THREADS on .NET here...see the topic. I push you on the PROFILING. but I know you don't understand what it means.

we don't normally say it tracelog... LOL...that's SUX! we call it PROFILING, see it here: http://en.wikipedia.org/wiki/Profili...er_programming)

I guess I have to introduce it here....

Use of profilers

The output of a profiler may be a stream of recorded events (a trace) or merely a statistical summary of the events observed (a profile) or an ongoing interaction with the hypervisor. Profilers use a wide variety of techniques to collect data, including hardware interrupts, code instrumentation, instruction set simulation, operating system hooks, and performance counters. The usage of profilers is 'called out' in the performance engineering process.

and that comes along with TRACING and LOGGING which you called it tracelog LOLZZZZZ but it is not just as simple as that.

That more you talk...the more It proves that you don't have such knowledge on this area.

[dodie]

it doesn't change the the issue that you don't trace your thread.
It doens't change that profiling is the tracelog itself. DUMBASS
trace logging is better..... DUMBASS

The more you talk, you are blinded.

[MarkCuering]

it doesn't change the the issue that you don't trace your thread.
It doens't change that profiling is the tracelog itself. DUMBASS
trace logging is better..... DUMBASS

what a shame... the only thing you are holding here is your tracelog LOL... go die for it dude... you cannot exchange little boy's lollipop with a BOOK

[dodie]

yeah right, stick to your own little world.

[MarkCuering]

yeah right, stick to your own little world.

How nice my little world is... I guess yours is too big, that you don’t even know what you are doing, thinking, talking… whew what a stupid paranoid.