![]() I don't think it will go down to per-line granularity though. Xperf will profile your native code and you can load your symbols into the result viewer. I'm waiting for someone to write a nice GUI around it, but it's taking a bit long. They have a steep learning curve but they are free and I doubt any commercial profiler can do what xperf can (the instrumentation is in the OS, not in a separate process, thus either Vista, win7 or win2K8 are required). If you are really serious about it you might look into the Microsoft xperf tools (). Net 4, But I doubt it can do a mixed profile of Native and Managed. However, I'm using a paid profiler, so the question will remain open until I take a look at xperf or someone comes up with something elseĪQTime have a free version of their latest profiler () It supports. UPDATE: After I cleaned my solution, built it again and checked all debug info (.pdb) was copied to the same directory as the executable, I tried AQTime again and it worked! It showed me routine timing info for both managed and unmanaged code, so my problem is solved. (I've spent the whole day stumped on this, sorry if I was too negative) I tried the "poor man's profiling" (halting the program many times and seeing where it is), but I get way too random results and I'm more used to traditional profiling.We use Visual Studio 2010 Professional SP1, so we don't have the Visual Studio profiler. ![]() NET 4.0 apps (it can't even start my app)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |