Dependency Walker on .NET applications: FlsAlloc

views:

309

answers:

+1 Q:

Dependency Walker on .NET applications: FlsAlloc

I have tried to profile several .NET executables in dependency walker and always get something like this:

GetProcAddress(0x7C800000 [KERNEL32.DLL], "FlsAlloc") called from "MSCOREE.DLL" at address 0x79006079 and returned 0xFFBADD11.

I tried making a new windows forms project VS2005 and did nothing but build it. Dependency walker still gives that same error. Does this mean that it is no longer possible to profile .Net applications, or am I missing something?

+2 A:

Dependency walker can only profile unmanaged programs.

Hans Passant 2010-01-14 20:01:39

Okay I can accept that :), any idea on a better way to track issues with managed dlls?

insipid 2010-01-14 20:26:34

Erm, a debugger?

Hans Passant 2010-01-14 20:34:38

I was referring to depedency problems, such as modules not being loaded and dlls not being found.

insipid 2010-01-14 20:57:19

The managed equivalent is Fuslogvw.exe

Hans Passant 2010-01-14 21:24:17

ansaurus

tags:

views:

answers:

Dependency Walker on .NET applications: FlsAlloc

related questions