Debuggers are often able to do things “normal” code can’t. You’d probably find that you can do this if you use the profiling/debugging API, but I don’t believe you can do it from “normal” .NET code.
More Related Contents:
- Automating the InvokeRequired code pattern
- Why is Thread.Sleep so harmful
- How do I abort/cancel TPL Tasks?
- Can a C# thread really cache a value and ignore changes to that value on other threads?
- BackgroundWorker RunWorkerCompleted Event
- How do I run a simple bit of code in a new thread?
- C# Thread Termination and Thread.Abort()
- C#: Waiting for all threads to complete
- How to protect resources that may be used in a multi-threaded or async environment?
- Set timeout to an operation
- What is a thread exit code?
- Does using Tasks (TPL) library make an application multithreaded?
- lock keyword in C#
- Wait for a while without blocking main thread
- Workaround for the WaitHandle.WaitAll 64 handle limit?
- Getting Cross-thread operation not valid [duplicate]
- Waiting for all threads to complete, with a timeout
- How to interrupt Console.ReadLine
- Error: Must create DependencySource on same Thread as the DependencyObject even by using Dispatcher
- Dispatcher Invoke(…) vs BeginInvoke(…) confusion
- How to access a WinForms control from another thread i.e. synchronize with the GUI thread?
- Locking pattern for proper use of .NET MemoryCache
- Is C# += thread safe?
- Write to a file from multiple threads asynchronously c#
- System.Timers.Timer/Threading.Timer vs Thread with WhileLoop + Thread.Sleep For Periodic Tasks
- InvalidOperationException – object is currently in use elsewhere – red cross
- Why does the inner exception reach the ThreadException handler and not the actual thrown exception?
- How does HttpContext.Current work in a multi-threaded environment?
- Wrapping ManualResetEvent as awaitable task
- Memory usage in C#