tag:blogger.com,1999:blog-18989586.post8239599799862387644..comments2022-03-29T16:35:51.735+02:00Comments on Windbg by Volker von Einem: Windbg 6.7.5.0 releasedVolker von Einemhttp://www.blogger.com/profile/03633759507649031608noreply@blogger.comBlogger5125tag:blogger.com,1999:blog-18989586.post-70322712067702629012013-12-05T10:37:53.154+01:002013-12-05T10:37:53.154+01:00This only works for CLR 2.0!
I still have a copy -...This only works for CLR 2.0!<br />I still have a copy - send me your email and you will get it.<br />I'm not using this anymore.Volker von Einemhttps://www.blogger.com/profile/03633759507649031608noreply@blogger.comtag:blogger.com,1999:blog-18989586.post-36257386122387851882013-12-05T07:45:29.049+01:002013-12-05T07:45:29.049+01:00I`m looking for a copy of the Windbg 6.7.5.0. to d...I`m looking for a copy of the Windbg 6.7.5.0. to do some C# source code debugging. Does anyone have a copy that can share with me? Really appreciated.<br /><br />-KenAnonymoushttps://www.blogger.com/profile/13734100557192479957noreply@blogger.comtag:blogger.com,1999:blog-18989586.post-67546096858381924932008-05-02T21:12:00.000+02:002008-05-02T21:12:00.000+02:00did someone say that clik a link and got right to ...did someone say that clik a link and got right to the source code for wnddbg??<BR/><BR/>is so, could you post the link, i don't see it at the wndbbg site..<BR/><BR/>thanksAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-18989586.post-26820716195145563712007-06-22T16:07:00.000+02:002007-06-22T16:07:00.000+02:00Hi Olivier,You hit a good point.The CLRStack -l/p/...Hi Olivier,<BR/><BR/>You hit a good point.<BR/><BR/>The CLRStack -l/p/a is kind of weak. Using -p (parameters) did a good job, but -l dumps just the stack address of the object pointer and the object pointer after the eqaul sign. You could for instance try to do a '!do 0x0129a58c'. That should give you the desired object. <BR/><BR/>For your local value types (0x0012f010 , 0x0012f014 ) I cannot give you a better hint than guessing or better looking at the disassembly to find out (by the PUSHes) which stack address corresponds with which of your variables.<BR/><BR/>I hope MS will come up with a better solution for that.Volker von Einemhttps://www.blogger.com/profile/03633759507649031608noreply@blogger.comtag:blogger.com,1999:blog-18989586.post-74838476572511653662007-06-20T17:57:00.000+02:002007-06-20T17:57:00.000+02:00Nice Blog;It helps me to understand how to work wi...Nice Blog;<BR/>It helps me to understand how to work with windbg.<BR/><BR/>I still have problem to manage the local variables<BR/><BR/>When I do !clrstack -l I get<BR/><BR/>0012f00c 7a6664ee System.Diagnostics.Process.WaitForExit()<BR/>0012f010 00e00d25 Dump.CMemoryDump.Dump10()<BR/> LOCALS:<BR/> 0x0012f018 = 0x0129a58c<BR/> <BR/> 0x0012f010 = 0x00000014<BR/> 0x0012f014 = 0x00000032<BR/><BR/>But i do not have the name of the local variables<BR/><BR/>When I try the command dv, I get<BR/>Private symbols (symbols.pri) are required for locals<BR/><BR/>Do you have any ideas how i can get the local variables<BR/><BR/>Thanks a lot<BR/><BR/>OlivierAnonymousnoreply@blogger.com