G\u00fcnler ge\u00e7iyor ve herhangi elle tutulur bir sonu\u00e7 hala alam\u0131yordum ve art\u0131k i\u015fin boyutu memory’den bir dump al\u0131p, bunu WinDBG<\/strong> arac\u0131l\u0131\u011f\u0131 ile analiz etmeye kalm\u0131\u015ft\u0131. Nerede ne ka\u00e7\u0131r\u0131yor olabilirdim acaba?<\/p>\n Evet i\u015fin hikaye boyutunu ge\u00e7ti\u011fimizde ise nedir bu\u00a0WinDBG<\/strong>\u00a0olay\u0131 bir bakmaya ba\u015flayarak sizlere deneyimlerimi aktarmaya \u00e7al\u0131\u015faca\u011f\u0131m. :)<\/p>\n Belle\u011fi (memory) t\u00fcketen uygulamalar\u0131n, herhangi bir “t”\u00a0an\u0131nda\u00a0al\u0131nan “g\u00f6r\u00fcnt\u00fcs\u00fcd\u00fcr” asl\u0131nda.<\/p><\/blockquote>\n Yukar\u0131daki tan\u0131mlamadan\u00a0yola \u00e7\u0131karsak, biz bu g\u00f6r\u00fcnt\u00fcye bakarak ortamda neler var?, neler \u00f6n plana \u00e7\u0131k\u0131yor?, neler arka planda kal\u0131yor?, neler daha \u00e7ok yer kaplarken, neler daha az yer kapl\u0131yor gibi resmin b\u00fct\u00fcn\u00fcn\u00fc g\u00f6rebilme \u015fans\u0131na sahip oluyoruz asl\u0131nda.<\/p>\n \u015eimdi makaleye ilk giri\u015fimdeki hikayeme tekrar bakt\u0131\u011f\u0131m\u0131zda ise; memory’de “t” an\u0131nda neler olup olmad\u0131\u011f\u0131n\u0131 anlayabilmem, yani resmin t\u00fcm\u00fcne bakabilmem i\u00e7in neden memory dump<\/strong> almaya ihtiya\u00e7 duydu\u011fumu\u00a0anlatabilmi\u015fimdir umar\u0131m.<\/p>\n \u00d6ncelikle buraya<\/a>\u00a0girerek “Get debugging tools” sekmesinde\u00a0bulunan Get Debugging Tools for Windows (WinDbg) (from the SDK)<\/strong>\u00a0ba\u011flant\u0131s\u0131na t\u0131klayarak, indirelim ve kurulumunu istedi\u011fimiz bir path’e (en az\u0131ndan 3-5 gb yer olan) ger\u00e7ekle\u015ftirelim.<\/p>\n Not: \u0130ndirme i\u015flemi biraz uzun s\u00fcrebilir. Bu ad\u0131mda otomatik olarak Windows Software Development Kit par\u00e7alar\u0131 indirilecektir.<\/p><\/blockquote>\n Kurulumu ger\u00e7ekle\u015ftirdikten sonra\u00a0WinDBG tool’u a\u00e7t\u0131\u011f\u0131n\u0131zda, yukar\u0131daki ekran ile kar\u015f\u0131la\u015facaks\u0131n\u0131z.<\/p>\n Bu eklenti bize, managed <\/strong>kod’lar\u0131 debug edebilme yetisini kazand\u0131racakt\u0131r. \u00c7\u00fcnk\u00fc default olarak WinDBG unmanaged<\/strong> kod’lar\u0131 debug etmek i\u00e7in tasarlanm\u0131\u015ft\u0131r ve win32 uygulamalar\u0131n\u0131n debugging’i i\u00e7in \u00e7ok kullan\u0131\u015fl\u0131d\u0131r bu komutlar. Default olarak gelen bu komutlar\u0131 .Net Framework ile geli\u015ftirilmi\u015f uygulamalar\u0131n debugging’i i\u00e7inde kullan\u0131labilir fakat olduk\u00e7a zor ve zahmetli bir i\u015ftir. \u0130\u015fte tam bu noktada biz developer’lar\u0131 d\u00fc\u015f\u00fcnerek, bu i\u015fi kolayla\u015ft\u0131racak extension’lar \u00e7\u0131kart\u0131lm\u0131\u015ft\u0131r. :)<\/p>\n Bu extension’lardan bir tanesi .Net Framework ile birlikte gelen SOS.dll<\/strong>‘dir ve\u00a0bize managed<\/strong> kodlar\u0131 ekstra komutlar ile nispeten daha kolay debug edebilmemizi sa\u011flamaktad\u0131r. Her g\u00fczel \u015feyin bir eksi\u011fi oldu\u011fu gibi SOS.dll’de debugging i\u015flemlerinde baz\u0131 noktalarda eksik kalmaktad\u0131r. \u0130\u015fte bu noktada PssCor2<\/strong> extension’u kullan\u0131larak, .Net<\/strong> uygulamalar\u0131n\u0131n debugging i\u015flemleri ekstra fonksiyonaliteler ile dahada kolayla\u015ft\u0131r\u0131lm\u0131\u015f ve SOS.dll’e g\u00f6re olan gap<\/strong>‘leri\u00a0giderilmi\u015ftir.<\/p>\n PssCor2 ayn\u0131 zamanda beraberinde\u00a0managed thread<\/strong>‘leri ve\u00a0managed object heap<\/strong>‘i izleme,\u00a0CLR stack<\/strong>‘i g\u00f6rebilme gibi ekstra \u00f6zelliklerini de\u00a0getirmektedir.<\/p>\n Ne i\u00e7in kullanmam\u0131z gerekti\u011fini anlad\u0131\u011f\u0131m\u0131za g\u00f6re \u015fimdi kurulum i\u015flemine ge\u00e7ebiliriz. \u00d6ncelikle buraya <\/a>t\u0131klayarak\u00a0Psscor2 Managed-Code Debugging Extension for WinDbg<\/strong>‘\u0131 indirelim. \u0130ndirme i\u015flemi bittikten sonra dosyay\u0131 unzip edelim. Unzip i\u015flemini tamamlad\u0131ktan\u00a0sonra “psscor2” klas\u00f6r\u00fcn\u00fc, daha \u00f6nceden kurulumunu yapm\u0131\u015f oldu\u011fumuz\u00a0WinDBG’\u0131n, ilgili kurulum dosyas\u0131n\u0131n i\u00e7erisinde\u00a0bulunan\u00a0“Debug” dosyas\u0131n\u0131n\u00a0i\u00e7erisine kopyalayal\u0131m.<\/p>\n \u00d6ncelikle neden Symbol dosyalar\u0131na ihtiya\u00e7 duyaca\u011f\u0131m\u0131za ge\u00e7meden\u00a0buraya <\/a>t\u0131klayarak, ilgili i\u015fletim sisteminize ve x86, x64 bit se\u00e7eneklerine dikkat ederek ilgili Symbol dosyalar\u0131n\u0131 indirmeye ba\u015flayal\u0131m.<\/p>\n Not: Symbol dosyalar\u0131n\u0131 indirme i\u015flemi zorunlu olmamakla beraber daha h\u0131zl\u0131 i\u015flem yapabilmeniz ad\u0131na indirmenizi tavsiye edip, makalenin ilerleyen b\u00f6l\u00fcmlerinde WinDBG i\u00e7erisinde nas\u0131l tan\u0131mlayabilece\u011fimizi\u00a0g\u00f6rece\u011fiz.<\/p><\/blockquote>\n Symbol dosyalar\u0131n\u0131 kabaca anlatmak gerekirse: Bu dosyalar uygulaman\u0131n compile s\u0131ras\u0131nda \u00fcretilirler. Bildi\u011fimiz gibi compile i\u015flemi s\u0131ras\u0131nda ise kodlar, IL(Intermediate Language) taraf\u0131ndan makine diline\u00a0\u00e7evrilir. Visual Studio ile derledi\u011fimizde de farkederseniz “bin\/debug” dosyas\u0131 alt\u0131nda “.PDB” uzant\u0131l\u0131 dosyalar olu\u015fmaktad\u0131r. \u0130\u015fte bu dosya assembly i\u00e7in debugging symbol’lerini i\u00e7ermektedir. \u0130\u00e7erisinde ise\u00a0identifier<\/strong>‘lar ve bu identifier’lar\u0131n assembly i\u00e7erisinde bulundu\u011fu yerler ve ayn\u0131 zamanda\u00a0attribute<\/strong>‘ler yer almaktad\u0131r.<\/p>\n Dump\u00a0i\u00e7erisinde\u00a0ise\u00a0sorununu ara\u015ft\u0131rd\u0131\u011f\u0131m\u0131z uygulaman\u0131n stack’i, hangi bellek adresinde bulundu\u011fu hexadecimal olarak tutulmaktad\u0131r ve o s\u0131rada ne yapmaya \u00e7al\u0131\u015ft\u0131\u011f\u0131n\u0131\u00a0anlayabilmemiz i\u00e7in gerekli bu t\u00fcm bilgiler \u00a0symbol dosyalar\u0131yla\u00a0\u015fekillenmektedir.<\/p>\n Symbol dosyalar\u0131n\u0131n indirme i\u015flemi tamamland\u0131ktan sonra, PssCor2 kurulumunda da yapt\u0131\u011f\u0131m\u0131z gibi WinDBG’\u0131 kurmu\u015f oldu\u011fumuz dosyan\u0131n i\u00e7erisindeki “Debug” dosyas\u0131n\u0131n i\u00e7erisine kurulumunu ger\u00e7ekle\u015ftirelim.<\/p>\n Sonunda as\u0131l k\u0131sm\u0131m\u0131za\u00a0ge\u00e7ebiliriz. Debugging i\u015flemlerini yapabilmemiz i\u00e7in gerekli olan her \u015fey haz\u0131r durumda. \u015eimdi bize problem yaratacak k\u00fc\u00e7\u00fck bir uygulama yazal\u0131m. :)<\/p>\n Ben basit bir Console uygulamas\u0131 tercih ettim. Bu kodda olas\u0131 hataya a\u00e7\u0131k olan k\u0131s\u0131mlar convert i\u015flemleri s\u0131ras\u0131nda herhangi bir kontrol\u00fcn yap\u0131lmamas\u0131ndan kaynaklanarak, runtime s\u0131ras\u0131nda kullan\u0131c\u0131 bazl\u0131 olu\u015fabilecek olan hatalard\u0131r. Zaten en \u00e7ok bu tarz hatalardan dolay\u0131 production ortamlar\u0131nda gol yemiyor muyuz?<\/p>\n Neyse konumuza geri d\u00f6nelim :) \u015eimdi haz\u0131rlam\u0131\u015f oldu\u011fumuz bu Console uygulamas\u0131n\u0131 bir iyi kullan\u0131c\u0131 g\u00f6z\u00fcnden kullanal\u0131m, birde k\u00f6t\u00fc kullan\u0131c\u0131 rol\u00fcnde kullan\u0131p do\u011fum tarihimizi yaz\u0131 ile yazal\u0131m. :)<\/p>\n ve tada… uygulamam\u0131z \u00e7\u00f6ker.<\/p>\n Buradaki hatay\u0131 herhangi bir try-catch blo\u011fu ile\u00a0kaybedede bilirdik ve i\u015fte ozaman bizim i\u00e7in\u00a0s\u0131k\u0131nt\u0131l\u0131 g\u00fcnler ba\u015flard\u0131. Hangi durumlar\u00a0kar\u015f\u0131s\u0131nda ne gibi\u00a0hatalar olu\u015fuyor? Ben bu problemi\u00a0nas\u0131l yakalayaca\u011f\u0131m? Her yere loglama koyma \u00e7abalar\u0131 ve dahas\u0131. Kullan\u0131c\u0131 kaynakl\u0131 olmayan bir hata da olabilirdi. Developer kaynakl\u0131 bir hataya ne derdiniz? A\u00e7\u0131k unutulmu\u015f ve dispose edilmemi\u015f bir obje? Belli bir y\u00fck alt\u0131nda memory leak<\/strong>‘lere sebep olabilir ve anlams\u0131z bir \u015fekilde uygulaman\u0131z\u0131n crash olmas\u0131na kadar sebep\u00a0verebilirdi\u00a0ve dahas\u0131 ve dahas\u0131. \u0130\u015fte bu gibi durumlar kar\u015f\u0131s\u0131nda\u00a0her ne kadar debugging i\u015flemi zor olsa da imdad\u0131m\u0131za WinDBG yeti\u015fiyor.<\/p>\n Uygulamam\u0131z \u00e7al\u0131\u015f\u0131r durumda iken dump nas\u0131l alabiliriz bir bakal\u0131m. “Ctrl+Alt+Delete” tu\u015f kombinasyonu ile “G\u00f6rev Y\u00f6neticisini” a\u00e7arak arka planda \u00e7al\u0131\u015fan process’lere bir bakal\u0131m. A\u00e7\u0131lan process listesinde uygulamam\u0131z\u0131n ad\u0131n\u0131 g\u00f6rmekteyiz “WinDbgTestApplication” olarak.<\/p>\n Not: Dump alaca\u011f\u0131n\u0131z uygulama bir windows form veya console uygulamas\u0131 olmayabilir. Bir web uygulamas\u0131 ise yine process’ler \u00fczerinden \u00f6rne\u011fin ilgili “w3wp.exe” veya localhost \u00fczerinde ise “iisexpress” in dump’lar\u0131n\u0131 da alabilmek m\u00fcmk\u00fcnd\u00fcr. (Ayn\u0131 zamanda \u00e7al\u0131\u015fan bir process’i attach edebilmekte m\u00fcmk\u00fcnd\u00fcr.)\u00a0Fakat bu \u015fekilde al\u0131nan\u00a0dump’lar\u0131 okumakta bi hayli zorlanabiliriz. Bunun yerine\u00a0IIS \u00fczerinden ilgili Application Pool’unu se\u00e7erek, “Debug Diagnostic Tool<\/strong>” gibi ara\u00e7lar ile daha kolay full memory dump’lar\u0131 alabilmek m\u00fcmk\u00fcnd\u00fcr.\u00a0Bu konuyu farkl\u0131 bir makalemde detayl\u0131 olarak aktaraca\u011f\u0131m. Bu makale kapsam\u0131nda herhangi bir dump nas\u0131l yorumlanabilir’i g\u00f6rece\u011fiz.<\/p><\/blockquote>\n G\u00f6rev Y\u00f6neticisi \u00fczerindeki process listesinde g\u00f6rm\u00fc\u015f oldu\u011fumuz uygulamam\u0131z\u0131n ad\u0131na sa\u011f t\u0131klayarak, ben windows 10 kulland\u0131\u011f\u0131m i\u00e7in “D\u00f6k\u00fcm dosyas\u0131 olu\u015ftur” se\u00e7ene\u011fine bas\u0131yorum.\u00a0E\u011fer farkl\u0131 bir windows versiyonu kullan\u0131yor iseniz, “Dump dosyas\u0131 olu\u015ftur” se\u00e7ene\u011fine basabilirsiniz.<\/p>\n Yukar\u0131daki resimde g\u00f6rebildi\u011fimiz gibi dump dosyam\u0131z\u0131, “AppData\/Local\/Temp” klas\u00f6r\u00fc alt\u0131nda “WinDbgTestApplication.DMP” olarak olu\u015fturmu\u015f durumdad\u0131r. Fakat bu \u015fekilde olu\u015fan dump’lar default olarak minidump<\/strong>‘d\u0131r. Bizim ise daha detayl\u0131 olarak full memory dumplar\u0131na<\/strong> ihtiyac\u0131m\u0131z vard\u0131r.<\/p>\n Full memory dumplar\u0131 alabilmek i\u00e7in \u00f6ncelikle buraya<\/a> t\u0131klayarak, “Process Explorer” \u0131 indirelim. \u0130ndirme i\u015flemini tamamlad\u0131ktan sonra unzip ederek i\u00e7erisinde bulunan uygulamay\u0131 \u00e7al\u0131\u015ft\u0131ral\u0131m. Bu i\u015flem sonunda t\u00fcm process’lerin daha detayl\u0131 bir \u015fekilde g\u00f6r\u00fcn\u00fcm\u00fcn\u00fcn\u00a0ekrana geldi\u011fini\u00a0g\u00f6rebiliriz. \u015eimdi listeden “WinDbgTestApplication” uygulamas\u0131n\u0131 bulal\u0131m ve ve sa\u011f t\u0131klayarak “Create Dump” men\u00fcs\u00fcnden “Create Full Dump” \u0131 se\u00e7elim.<\/p>\n Create Full Dump ad\u0131m\u0131ndan sonra istedi\u011fimiz bir path’e dump dosyam\u0131z\u0131 kaydedelim. Art\u0131k elimizde WinDbgTestApplication uygulamas\u0131na dair full memory dump’\u0131 bulunmaktad\u0131r.<\/p>\n Uygulamalar\u0131m\u0131z k\u0131sm\u0131ndan WinDbg (x86)’y\u0131 se\u00e7elim ve \u00e7al\u0131\u015ft\u0131ral\u0131m. Uygulamam\u0131z \u00e7al\u0131\u015ft\u0131ktan sonra ilk \u00f6nce indirmi\u015f oldu\u011fumuz Symbol dosyas\u0131n\u0131 tan\u0131mlayal\u0131m. Bunu ger\u00e7ekle\u015ftirebilmek i\u00e7in sol \u00fcstte bulunan “File” sekmesine t\u0131klayarak ard\u0131ndan “Symbol File Path” se\u00e7ene\u011fine t\u0131klayal\u0131m.<\/p>\n A\u00e7\u0131lan pencerede “Symbol path” k\u0131sm\u0131na symbol yolunu belirtme syntax’\u0131 \u015fu \u015fekildedir:<\/p>\n Ben kurulumumu WinDBG i\u00e7erisinde bulunan “Debug” klas\u00f6r\u00fc alt\u0131nda yapt\u0131\u011f\u0131m i\u00e7in \u015fu \u015fekilde path bilgisini giriyorum.<\/p>\n \u015eimdi s\u0131ra alm\u0131\u015f oldu\u011fumuz dump’\u0131n import i\u015fleminde. Bunun i\u00e7inde yine WinDBG uygulamas\u0131n\u0131n sol \u00fcst\u00fcnde bulunan “File” men\u00fcs\u00fcne t\u0131klayarak ard\u0131ndan “Open Crash Dump” se\u00e7ene\u011fine t\u0131kl\u0131yoruz. Ard\u0131ndan\u00a0olu\u015fturmu\u015f oldu\u011fumuz\u00a0dump dosyam\u0131z\u0131 burada import ediyoruz. (Ben dosyaya daha kolay eri\u015febilmek ad\u0131na masa\u00fcst\u00fcme ta\u015f\u0131d\u0131m.)<\/p>\n Dump dosyas\u0131n\u0131n import i\u015flemi sonras\u0131nda ekranda kar\u015f\u0131m\u0131za \u015fu komut sat\u0131rlar\u0131 gelecektir:<\/p>\n \u015eimdi WinDBG arac\u0131m\u0131z i\u00e7in indirmi\u015f oldu\u011fumuz PssCor2 extension’\u0131n\u0131\u00a0dahil edelim. PssCor2 indirme k\u0131sm\u0131nda da\u00a0bahsetti\u011fimiz gibi\u00a0bu extension sayesinde .Net ile\u00a0geli\u015ftirmi\u015f oldu\u011fumuz uygulamam\u0131z\u0131 bize sa\u011flayaca\u011f\u0131 ek fonksiyonaliteler ile daha kolay debug i\u015flemlerini ger\u00e7ekele\u015ftirecek idik.<\/p>\n WinDBG i\u00e7erisine PssCor2’yi dahil edebilmek i\u00e7in\u00a0a\u015fa\u011f\u0131daki komut’u, WinDBG uygulamas\u0131n\u0131n alt b\u00f6l\u00fcm\u00fcnde bulunan komut sat\u0131r\u0131\u00a0k\u0131sm\u0131na girmemiz yeterli olacakt\u0131r.<\/p>\n Not: PssCor2 y\u00fckleme i\u015flemi s\u0131ras\u0131nda uygulaman\u0131z\u0131n\u00a0bit’ine g\u00f6re ilgili PssCor2’yi se\u00e7meniz\u00a0\u00f6nemlidir. Console uygulamam\u0131z 32 bit\u00a0oldu\u011fu i\u00e7in “x86” se\u00e7ene\u011fini y\u00fckl\u00fcyorum.<\/p><\/blockquote>\n Y\u00fckleme i\u015fleminin ard\u0131ndan PssCor2’nin ba\u015far\u0131l\u0131 bir \u015fekilde y\u00fcklenip y\u00fcklenilmedi\u011fini anlayabilmek i\u00e7in komut k\u0131sm\u0131nda “!help” komutunu girerek \u00e7al\u0131\u015ft\u0131ral\u0131m.<\/p>\n Y\u00fckleme i\u015flemi ba\u015far\u0131l\u0131 ise yukar\u0131daki \u015fekilde yard\u0131m komutlar\u0131 ekrana gelecektir.<\/p>\n \u015eimdi s\u0131ra “mscordacwks.dll<\/strong>” i y\u00fcklemeye geldi. Mscordacwks kabaca t\u0131pk\u0131 “SOS.dll” de oldu\u011fu gibi WinDBG arac\u0131m\u0131zda debugging i\u015flemlerimiz i\u00e7in CLR ayr\u0131nt\u0131lar\u0131 \u00fczerinde bize data-access abstraction’\u0131 sa\u011flamaktad\u0131r. Bu ayr\u0131nt\u0131ya tak\u0131lmam\u0131za gerek yoktur.<\/p>\n Y\u00fckleme i\u015flemini a\u015fa\u011f\u0131daki komut\u00a0ile ger\u00e7ekle\u015ftirebiliriz:<\/p>\n Ba\u015far\u0131l\u0131 ile y\u00fcklendi\u011finde a\u015fa\u011f\u0131daki komut sat\u0131r\u0131 ekrana gelecektir.<\/p>\n Not: “mscordacwks.dll” y\u00fckleme s\u0131ras\u0131nda e\u011fer “SOS does not support the current target architecture.” gibi bir hata al\u0131rsan\u0131z, uygulaman\u0131z\u0131n bit de\u011ferlerine g\u00f6re do\u011fru PssCor2’yi y\u00fckledi\u011finizden emin olmal\u0131s\u0131n\u0131z.<\/p><\/blockquote>\n Evet her \u015fey haz\u0131r oldu\u011funa g\u00f6re art\u0131k CLR Stack’i inceleyebiliriz. \u00a0A\u015fa\u011f\u0131daki komut sat\u0131r\u0131 ile managed stack’i listeleyebiliriz.<\/p>\n Bu i\u015flem sonucunda a\u015fa\u011f\u0131daki gibi bir \u00e7\u0131kt\u0131 ile kar\u015f\u0131la\u015faca\u011f\u0131z:<\/p>\n Ekran g\u00f6r\u00fcnt\u00fcs\u00fc ise a\u015fa\u011f\u0131daki gibidir.<\/p>\n tada… art\u0131k managed stack kar\u015f\u0131m\u0131zda.\u00a0Evet \u015fimdi bunlar\u0131 nas\u0131l yorumlayaca\u011f\u0131z k\u0131sm\u0131na gelelim.<\/p>\n Uygulamam\u0131z\u0131n dump alma i\u015flemi s\u0131ras\u0131nda \u00e7al\u0131\u015fan thread’lere bir bakal\u0131m \u00f6ncelikle. Bunun i\u00e7in a\u015fa\u011f\u0131daki komut sat\u0131r\u0131n\u0131 girmemiz yeterlidir.<\/p>\n Bu i\u015flemin sonucunda a\u015fa\u011f\u0131daki gibi thread’ler ekrana gelmektedir.<\/p>\n Ekrana gelen bu managed thread’lere bakt\u0131\u011f\u0131m\u0131zda:<\/p>\n “1” id’li olan managed thread’in exception ba\u015fl\u0131\u011f\u0131 alt\u0131nda “System.FormatException” verdi\u011fini a\u00e7\u0131k\u00e7a g\u00f6rebilmekteyiz. \u015eimdi bu hatan\u0131n detay\u0131na biraz daha inmek istersek e\u011fer a\u015fa\u011f\u0131daki komut sat\u0131r\u0131n\u0131 girmemiz yeterli olacakt\u0131r.<\/p>\n Bu komutun sonucunda ise exception detay\u0131 a\u015fa\u011f\u0131daki gibi kar\u015f\u0131m\u0131za \u00e7\u0131kacakt\u0131r. :)<\/p>\n Evet\u00a0uygulamam\u0131z\u0131n crash olmas\u0131na sebep olan exception detaylar\u0131na git gide yakla\u015fmaktay\u0131z. \u0130lk ba\u015fta “!clrstack” komutu ile karma\u015f\u0131k gelen managed stack’den yola \u00e7\u0131karak git gide stack’i\u00a0anlamland\u0131rmaya ba\u015flad\u0131k. StackTrace<\/strong> k\u0131sm\u0131nda g\u00f6rebildi\u011fimiz gibi “System.Number.StringToNumber” fonksiyonu ile string’den int’e convert i\u015flemi s\u0131ras\u0131nda bir hatan\u0131n meydana geldi\u011fini g\u00f6rmekteyiz.<\/p>\n Dilersek bu i\u015flem s\u0131ras\u0131nda bu fonksiyonlar\u0131n hangi parametreler ve ilgili de\u011fi\u015fkenleri ile beraber\u00a0\u00e7a\u011fr\u0131ld\u0131\u011f\u0131n\u0131 da a\u015fa\u011f\u0131daki kod blo\u011fu ile alabilmek m\u00fcmk\u00fcnd\u00fcr.<\/p>\n Bu i\u015flem sonucunda ise a\u015fa\u011f\u0131daki gibi bir kod ekran\u0131 kar\u015f\u0131m\u0131za gelecektir.<\/p>\n![\"debugging-windbg\"](\"\/wp-content\/uploads\/2016\/05\/debugging-windbg.gif\")
<\/a><\/p>\nNedir Bu Memory Dump?<\/h4>\n
WinDBG’a Ba\u015flang\u0131\u00e7 ve Kurulum<\/h4>\n
<\/a><\/p>\nPssCor2 Nedir? ve Kurulumu<\/h4>\n
<\/a><\/p>\nSymbol Path’in Ayarlanmas\u0131<\/h4>\n
<\/a><\/p>\nusing System;\r\n\r\nnamespace WinDbgTestApplication\r\n{\r\n class Program\r\n {\r\n static void Main(string[] args)\r\n {\r\n while (true)\r\n {\r\n Console.WriteLine(\"Do\u011fum y\u0131l\u0131n\u0131z\u0131 giriniz:\");\r\n\r\n int birthYear = Convert.ToInt32(Console.ReadLine());\r\n int currentYear = DateTime.Today.Year;\r\n int result = currentYear - birthYear;\r\n\r\n Console.WriteLine(\"{0} ya\u015f\u0131ndas\u0131n\u0131z.\", result);\r\n }\r\n }\r\n }\r\n}<\/pre>\n<\/a><\/p>\nDump Alma<\/h4>\n
<\/a><\/p>\nProcess Explorer<\/h4>\n
<\/a><\/p>\nWinDBG’\u0131 Ke\u015ffetmeye Ba\u015flayal\u0131m<\/h4>\n
srv*[kurulum yap\u0131lan local symbol path'i]*http:\/\/msdl.microsoft.com\/download\/symbols<\/pre>\n
srv*f:\\wdk\\debug\\symbols*http:\/\/msdl.microsoft.com\/download\/symbols<\/pre>\n
<\/a><\/p>\nMicrosoft (R) Windows Debugger Version 10.0.10586.567 X86\r\nCopyright (c) Microsoft Corporation. All rights reserved.\r\n\r\n\r\nLoading Dump File [C:\\Users\\G\u00d6KALP\\Desktop\\WinDbgTestApplication-Full.dmp]\r\nUser Mini Dump File with Full Memory: Only application data is available\r\n\r\n\r\n************* Symbol Path validation summary **************\r\nResponse Time (ms) Location\r\nDeferred srv*f:\\wdk\\debug\\symbols*http:\/\/msdl.microsoft.com\/download\/symbols\r\nSymbol search path is: srv*f:\\wdk\\debug\\symbols*http:\/\/msdl.microsoft.com\/download\/symbols\r\nExecutable search path is: \r\nWindows 10 Version 10586 MP (4 procs) Free x86 compatible\r\nProduct: WinNt, suite: SingleUserTS Personal\r\nBuilt by: 10.0.10586.0 (th2_release.151029-1700)\r\nMachine Name:\r\nDebug session time: Sun May 8 16:35:28.000 2016 (UTC + 3:00)\r\nSystem Uptime: 3 days 16:21:05.267\r\nProcess Uptime: 0 days 0:01:01.000\r\n..................................\r\neax=00000000 ebx=00000000 ecx=00000005 edx=00000000 esi=00000003 edi=00000003\r\neip=7773718c esp=0018e3e8 ebp=0018e578 iopl=0 nv up ei pl nz na pe nc\r\ncs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000206\r\nntdll!NtWaitForMultipleObjects+0xc:\r\n7773718c c21400 ret 14h<\/pre>\n
.load f:\\wdk\\debug\\psscor2\\x86\\psscor2.dll<\/pre>\n
<\/a><\/p>\n.cordll -ve -u -l<\/pre>\n
0:000> .cordll -ve -u -l\r\nAutomatically loaded SOS Extension\r\nCLRDLL: Loaded DLL C:\\Windows\\Microsoft.NET\\Framework\\v4.0.30319\\mscordacwks.dll\r\nCLR DLL status: Loaded DLL C:\\Windows\\Microsoft.NET\\Framework\\v4.0.30319\\mscordacwks.dll<\/pre>\n
CLR Stack’i \u0130nceleme Zaman\u0131<\/h4>\n
!clrstack<\/pre>\n
0:000> !clrstack\r\nOS Thread Id: 0x314c (0)\r\nChild SP IP Call Site\r\n0018f1f0 7773718c [HelperMethodFrame: 0018f1f0] \r\n0018f2a0 720acc3a System.Number.StringToNumber(System.String, System.Globalization.NumberStyles, NumberBuffer ByRef, System.Globalization.NumberFormatInfo, Boolean)\r\n0018f2c8 7156fe79 System.Number.ParseInt32(System.String, System.Globalization.NumberStyles, System.Globalization.NumberFormatInfo)\r\n0018f378 71bfd34a System.Convert.ToInt32(System.String)\r\n0018f384 00d804ab *** WARNING: Unable to verify checksum for WinDbgTestApplication.exe\r\nWinDbgTestApplication.Program.Main(System.String[]) [C:\\Users\\G\u00d6KALP\\Documents\\Visual Studio 2015\\Projects\\WinDbgTestApplication\\WinDbgTestApplication\\Program.cs @ 13]\r\n0018f538 72671376 [GCFrame: 0018f538]<\/pre>\n
<\/a><\/p>\n!threads<\/pre>\n
<\/a><\/p>\n0:000> !threads\r\nThreadCount: 2\r\nUnstartedThread: 0\r\nBackgroundThread: 1\r\nPendingThread: 0\r\nDeadThread: 0\r\nHosted Runtime: no\r\n Lock \r\n ID OSID ThreadOBJ State GC Mode GC Alloc Context Domain Count Apt Exception\r\n 0 1 314c 00be98a8 2a020 Preemptive 02613E9C:00000000 00be3ed8 0 MTA System.FormatException 0260b2c4\r\n 5 2 2168 00bf77a8 2b220 Preemptive 00000000:00000000 00be3ed8 0 MTA (Finalizer)<\/pre>\n
!printexception<\/pre>\n
0:000> !printexception\r\nException object: 0260b2c4\r\nException type: System.FormatException\r\nMessage: Giri\u015f dizesi do\u011fru bi\u00e7imde de\u011fildi.\r\nInnerException: <none>\r\nStackTrace (generated):\r\n SP IP Function\r\n 0018F2A0 720ACC39 mscorlib_ni!System.Number.StringToNumber(System.String, System.Globalization.NumberStyles, NumberBuffer ByRef, System.Globalization.NumberFormatInfo, Boolean)+0xb3cd59\r\n 0018F2C8 7156FE79 mscorlib_ni!System.Number.ParseInt32(System.String, System.Globalization.NumberStyles, System.Globalization.NumberFormatInfo)+0x79\r\n 0018F378 71BFD34A mscorlib_ni!System.Convert.ToInt32(System.String)+0x32\r\n 0018F384 00D804AB WinDbgTestApplication!WinDbgTestApplication.Program.Main(System.String[])+0x63\r\n\r\nStackTraceString: <none>\r\nHResult: 80131537<\/pre>\n
!clrstack -a<\/pre>\n