Windows 7 - windbg and sos 2.0 - where are my line numbers?

Asked By Satis

01-Aug-07 07:08 PM

can someone help me understand the circumstances where !clrstack will show
line numbers?

I just recently upgraded to windbg 6.5.1, and am not sure if something broke
there.

Basically, i have a managed windows form app (written for demo purposes)
with a few lines of code, compiled into a release build with symbols
(pdb-only). I also have the debug build.

If I attach windbg to this process, load sos 2.0, and run !clrstack, i see
no line numbers. The symbols for the EXE have been loaded, and the "lm"
output says "private pdb symbols"

Another behavior has also dissaperared.. aka if I run "k", my previous
experience with windbg was that it would actually show the managed call stack
and mix it with the native call stack, kind of like "!dumpstack".. this is
also not working anymore.

What changed???!!

04-Aug-07 08:21 AM

Apparently this is a known bug of the 6.7.5.1 debugger release.
Revert to 6.7.5.0 to restore integrated managed debugging
functionality.
See http://voneinem-windbg.blogspot.com/2007/07/first-look-at-windbg-6751-disappointing.html

Koby Kahane

06-Aug-07 12:24 PM

Hello Satish.

Sos is not something that ships with the debugging tools package.  Could you
tell us from where you got this item and what the version information is for
it?

.pat styles [microsoft]

can someone help me understand the circumstances where !clrstack will show
line numbers?

I just recently upgraded to windbg 6.5.1, and am not sure if something broke
there.

Basically, i have a managed windows form app (written for demo purposes)
with a few lines of code, compiled into a release build with symbols
(pdb-only). I also have the debug build.

If I attach windbg to this process, load sos 2.0, and run !clrstack, i see
no line numbers. The symbols for the EXE have been loaded, and the "lm"
output says "private pdb symbols"

Another behavior has also dissaperared.. aka if I run "k", my previous
experience with windbg was that it would actually show the managed call
stack
and mix it with the native call stack, kind of like "!dumpstack".. this is
also not working anymore.

What changed???!!

06-Aug-07 02:02 PM

yeah I saw that.. i rolled back to 6.7.5.0 and I now have line numbers..
definitely a bug in 6.7.5.1.

06-Aug-07 02:04 PM

Pat,
the debugging tools package comes with an updated 1.1 release of SOS in the
clr10 directory.

The 2.0 version is from the framework directory.

If someone in msft is listening, please publish an updated sos extension for
2.0, that atleast features some of the commands in clr10\sos.

We all really need some simple commands to dump ASP.NET stuff, like the
request table, cache etc.

06-Aug-07 05:56 PM

Hello Koby.

The behavior you are describing in this post and your blog is not a bug.
WinDbg does not now and never has supported the debugging of managed code,
outside the functionality in sos 1.x that ships with the debugger package.
That said, some versions of the debugger may have exhibited features that
seemed to work with .NET targets.  This is inadvertent and not the result of
any intention to add functionality that works with managed code.  If you
found that 6.7.5.0 exhibited a feature in respect to managed code that was
not available in other versions, please understand that it is not deliberate
or supported.  This is something that we hope to add in future, but we are
not there yet.

.pat styles [microsoft]


Apparently this is a known bug of the 6.7.5.1 debugger release.
Revert to 6.7.5.0 to restore integrated managed debugging
functionality.
See
http://voneinem-windbg.blogspot.com/2007/07/first-look-at-windbg-6751-disappointing.html

Koby Kahane

03-Apr-08 02:00 PM

Hi Pat!

Any news about support for managed code in windbg?

Will there be a release which supports the display of line numbers for
managed code?

Or missed I something? I can't get it to work, even with debug-builds
and full-dumps...


Here is your reply to some post here regarding this issue:
http://voneinem-windbg.blogspot.com/2007/07/first-look-at-windbg-6751-disappointing.html


Origincal message:

Satish schrieb:


--
Greetings
Jochen

My blog about Win32 and .NET
http://blog.kalmbachnet.de/