Browse by Tags

• Rotor code explanation

• Thread, System.Threading.Thread, and !Threads (III)

  I got email asking me to explain !Threads output in details. I think this is a good question and a good topic for another installment to the series. Here is an example I'll use for this post: 0:055> !threads ThreadCount: 202 UnstartedThread: 95 BackgroundThread: Read More... Posted Tuesday, August 30, 2005 9:55 AM by yunjin | 5 Comments Filed under: Rotor code explanation, .NET programming gotcha and debugging tips, CLR internal and Misc

• Thread, System.Threading.Thread, and !Threads (II)

  With knowledge in my previous blog , we could avoid some mistakes in .NET programming. A C++ Thread is very resource heavy. It is associated with a lot of dynamically allocated memory and some OS handles. So it had better to be cleaned up ASAP after its Read More... Posted Monday, August 29, 2005 9:30 AM by yunjin | 2 Comments Filed under: Rotor code explanation, .NET programming gotcha and debugging tips, CLR internal and Misc

• Thread, System.Threading.Thread, and !Threads (I)

  If you use SOS’s !Threads command during debugging a lot, you should be familiar with such output: 0:003> !threads PDB symbol for mscorwks.dll not loaded Loaded Son of Strike data table version 5 from "C:\WINDOWS\Microsoft.NET\Framework\v1.1.4322\mscorwks.dll" Read More... Posted Thursday, August 25, 2005 10:26 AM by yunjin | 4 Comments Filed under: Rotor code explanation, .NET programming gotcha and debugging tips, CLR internal and Misc

• Figure out variable lifetime using SOS

  There is a bug in this program below, try to see if you could catch it. Test.cs (compiled to DelegateExample.exe): using System; using System.Threading; using System.Runtime.InteropServices; class Test { delegate uint ThreadProc (IntPtr arg); private Read More... Posted Sunday, May 15, 2005 1:06 AM by yunjin | 3 Comments Filed under: .NET programming gotcha and debugging tips, CLR internal and Misc

• Thread safety of Timer callbacks

  I didn't realize I've stopped blogging for 1 year. What a shame! Fortunately I didn’t waste the time: we ship Whidbey Beta1 and Beta2 in the past year! Now with Beta2 out of door, I have more spare time for blogging. :) Today I want to talk about some Read More... Posted Sunday, May 08, 2005 2:12 AM by yunjin | 5 Comments Filed under: Rotor code explanation, .NET programming gotcha and debugging tips, CLR internal and Misc

• Dangerous PInvokes - string modification

  Objects in CLR are usually managed by the runtime in GC heap; user code does not have direct access to the objects. CLR's reliability and type safety heavily rely on this fact. But CLR also support InterOp features like COM InterOp, IJW and PInvoke to Read More... Posted Saturday, February 21, 2004 4:30 PM by yunjin | 5 Comments Filed under: .NET programming gotcha and debugging tips, CLR internal and Misc

• OutOfMemoryException and Pinning

  As you all know, in CLR memory management is done by Garbage collector (GC). When GC can't find memory in preallocated memory chunk (GC heap) for new objects and can't book enough memory from the OS to expand GC heap, it throws OutOfMemoryException (OOM). Read More... Posted Tuesday, January 27, 2004 8:52 PM by yunjin | 10 Comments Filed under: .NET programming gotcha and debugging tips, CLR internal and Misc