Skip to main content

Debugging multithreaded applications in Visual Studio

In postul precedent am povestit putin despre cateva lucruri de baza cand facem debug in Visual Studio. Astazi o sa continuam aceasta discutie si o sa vedem cum putem face debug intr-un mediu multi-thread si multi-processor.
Cand lucram cu mai multe thread-uri, fereastra "Threads" devine cea mai buna prietena a noastra. Prin intermediul acesteia, cand aplicatia ajunge la un breakpoint putem sa vedem toate thread-urile active in procesul nostru. Pentru fiecare thread, putem sa vedem numele acestuia, ID-ul prioritatea si nu in ultimul rand call stack-ul pentru fiecare thread in parte (numele la coloana este "Location"). De foarte multe ori callstack-ul ne ajuta foarte mult nemaifiind nevoie sa selectam cate un thread in parte pentru a vedea callstack-ul.
In momentul cand suntem intr-un breakpoint sa nu uitati ca restul thread-urile ruleaza in continuare. In dreapta acestei ferestre avem un buton "Freeze" prin intermediul caruia putem sa facem freeze la toate thread-urile din procesul nostru. Nu odata mi s-a intamplat ca pana sa investighez codul care rula dintr-un thread, unul sau mai multe thread-uri s-au terminat de executat, iar problema pe care o aveam nu o mai puteam reproduce. Cand un thread este selectat din lista, Visual Studio o sa incerce sa va dupa la codul care se ruleaza pentru thread-ul vostru.

O fereastra asemanatoare exista si pentru procese. In mod normal o sa fiti legati la un sigur proces, caz in care o sa aveti un singur proces in lista. 2 sau mai multe procese pot sa fie active cand aveti mai multe procese selectate de a rula la RUN sau cand va atasati manual la alte procese. 
Toate modulele (assembly-urile) care sunt incarcate intr-un anumit moment pot sa fie vizualizate din fereastra Modules. Aceasta fereastra este folositoare daca aveti probleme cu versiune de assembly sau nu stiti exact ce assembly se incarca si din ce locatie. Aceasta fereastra poate sa deschisa din "Debug->Windows->Modules".
Cand executati codul step cu step si aveti mai multe thread-uri pornite sa nu uitati ca restul thread-urilor ruleza normal daca nu ati facut freeze. Iar in cazul in care un alt thread ajunge la un breakpoint, atunci o sa va intrati pe thread-ul respectiv. Puteti specifica pe un breakpoint pe ce thread sa se activeze (in postul precedent am discutat despre acest lucru).
In cazul in care aveti mai multe thread-uri puteti sa folositi fereastra de "Parallel Stacks" fara nici o problema, chiar daca nu folositi librarie de paralle library. Aceasta va afiseaza un stack pentru modul in care thread-urile au fost create si ce thread pe care il asteapta.
Cand faceti debug incercati ca numarul de thread-uri pe care le aveti pornite sa fie cat mai mic (3-4). Daca o sa aveti prea multe thread-uri pornite, procesul de debug o sa fie destul de complex.
In urmatorul post o sa discutam despre Debugger Canvas.

Comments

Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…

GET call of REST API that contains '/'-slash character in the value of a parameter

Let’s assume that we have the following scenario: I have a public HTTP endpoint and I need to post some content using GET command. One of the parameters contains special characters like “\” and “/”. If the endpoint is an ApiController than you may have problems if you encode the parameter using the http encoder.
using (var httpClient = new HttpClient()) { httpClient.BaseAddress = baseUrl; Task<HttpResponseMessage> response = httpClient.GetAsync(string.Format("api/foo/{0}", "qwert/qwerqwer"))); response.Wait(); response.Result.EnsureSuccessStatusCode(); } One possible solution would be to encode the query parameter using UrlTokenEncode method of HttpServerUtility class and GetBytes method ofUTF8. In this way you would get the array of bytes of the parameter and encode them as a url token.
The following code show to you how you could write the encode and decode methods.
publ…