nprof - Project Hosting on Google Code

Older Sep 21, 2009 r291 (comparison bugfixes) committed by staudenmeyer - comparison bugfixes comparison bugfixes Sep 14, 2009 issue 12 (Support for .NET 4.0) Labels changed by staudenmeyer - Labels: Milestone-0.13 Labels: Milestone-0.13 Sep 14, 2009 issue 11 (Instrumentation profiling) Labels changed by staudenmeyer - Labels: Milestone-0.13 Labels: Milestone-0.13 Sep 14, 2009 issue 10 (Pause and reset) Labels changed by staudenmeyer - Labels: Milestone-0.13 Labels: Milestone-0.13 Sep 14, 2009 issue 9 (Improve accuracy on Windows Vista) Labels changed by staudenmeyer - Labels: Milestone-0.12 Labels: Milestone-0.12 Sep 14, 2009 issue 5 (Inner classes in signatures) Labels changed by staudenmeyer - Labels: Milestone-0.12 Labels: Milestone-0.12 Sep 14, 2009 issue 3 (Generics) Labels changed by staudenmeyer - Labels: Milestone-0.12 −Milestone-Release0.12 Labels: Milestone-0.12 −Milestone-Release0.12 Sep 14, 2009 issue 4 (Compare profiler runs) Labels changed by staudenmeyer - Labels: Milestone-0.12 −Milestone-012 Labels: Milestone-0.12 −Milestone-012 Sep 14, 2009 issue 4 (Compare profiler runs) Labels changed by staudenmeyer - Labels: Milestone-012 Labels: Milestone-012 Sep 14, 2009 issue 3 (Generics) Labels changed by staudenmeyer - Labels: Milestone-Release0.12 Labels: Milestone-Release0.12 Sep 14, 2009 issue 12 (Support for .NET 4.0) Owner changed by staudenmeyer - Owner: --- Owner: --- Sep 14, 2009 issue 11 (Instrumentation profiling) Owner changed by staudenmeyer - Owner: --- Owner: --- Sep 14, 2009 issue 5 (Inner classes in signatures) Owner changed by staudenmeyer - Owner: --- Owner: --- Sep 14, 2009 issue 3 (Generics) Owner changed by staudenmeyer - Owner: --- Owner: --- Sep 14, 2009 issue 10 (Pause and reset) commented on by staudenmeyer - It should be possible to implement this using the attach / detach feature in the .NET 4.0 profiling API (see http://blogs.msdn.com/davbr/archive/2008/11/10/new- stuff-in-profiling-api-for-upcoming-clr-4-0.aspx). This would also be useful to profile production web servers, for example. It should be possible to implement this using the attach / detach feature in the .NET 4.0 profiling API (see http://blogs.msdn.com/davbr/archive/2008/11/10/new- stuff-in-profiling-api-for-upcoming-clr-4-0.aspx). This would also be useful to profile production web servers, for example. Sep 14, 2009 issue 2 (Exclusive time) Status changed by staudenmeyer - Status: WontFix Status: WontFix Sep 14, 2009 issue 12 (Support for .NET 4.0) reported by staudenmeyer - NProf should support profiling of .NET 4.0 applications. NProf should support profiling of .NET 4.0 applications. Sep 14, 2009 issue 11 (Instrumentation profiling) reported by staudenmeyer - In addition to sampling, NProf should also support instrumentation profiling. In .NET 4.0 the performance of instrumentation profiling should be improved (see http://blogs.msdn.com/davbr/archive/2008/11/10/new-stuff-in- profiling-api-for-upcoming-clr-4-0.aspx). In addition to sampling, NProf should also support instrumentation profiling. In .NET 4.0 the performance of instrumentation profiling should be improved (see http://blogs.msdn.com/davbr/archive/2008/11/10/new-stuff-in- profiling-api-for-upcoming-clr-4-0.aspx). Sep 14, 2009 r290 (added profile run comparisons) committed by staudenmeyer - added profile run comparisons added profile run comparisons Aug 15, 2009 issue 10 (Pause and reset) reported by coldequation - By allowing manual pausing and resting of profiling, nprof would be much more useful for applications with lengthy start up times or specific trouble spots. By allowing manual pausing and resting of profiling, nprof would be much more useful for applications with lengthy start up times or specific trouble spots. Jul 18, 2009 r289 ([No log message]) committed by staudenmeyer - [No log message] [No log message] Jul 15, 2009 r288 ([No log message]) committed by staudenmeyer - [No log message] [No log message] Jul 14, 2009 issue 9 (Improve accuracy on Windows Vista) reported by staudenmeyer - On Windows Vista and above, use the QueryThreadCycleTime function instead of GetThreadTimes to improve the accuracy of the profiler. On Windows Vista and above, use the QueryThreadCycleTime function instead of GetThreadTimes to improve the accuracy of the profiler. Jul 14, 2009 r287 ([No log message]) committed by staudenmeyer - [No log message] [No log message] Jul 14, 2009 r286 ([No log message]) committed by staudenmeyer - [No log message] [No log message] Jul 14, 2009 issue 6 (NProf is inaccurate) Status changed by staudenmeyer - The accuracy of NProf has been improved in NProf 0.11. The accuracy is still somewhat limited by the resolution and accuracy of GetThreadTimes, however. Status: Fixed The accuracy of NProf has been improved in NProf 0.11. The accuracy is still somewhat limited by the resolution and accuracy of GetThreadTimes, however. Status: Fixed Jul 14, 2009 issue 7 (Start profiled app with specified working directory) changed by staudenmeyer - This problem has been fixed in NProf 0.11. Status: Fixed Owner: staudenmeyer This problem has been fixed in NProf 0.11. Status: Fixed Owner: staudenmeyer Jul 14, 2009 issue 8 (Nprof doesn't work on Vista-64. ) Status changed by staudenmeyer - This has been fixed in NProf 0.11. Status: Fixed This has been fixed in NProf 0.11. Status: Fixed Jul 14, 2009 NProf 0.11 Source.zip (NProf 0.11 source) file uploaded by staudenmeyer - Labels: Type-Source Labels: Type-Source Jul 14, 2009 NProf-0.11-Setup.exe (NProf 0.11 installer) file uploaded by staudenmeyer - Labels: Featured Type-Executable Labels: Featured Type-Executable Jun 29, 2009 issue 8 (Nprof doesn't work on Vista-64. ) commented on by lagattack - The proposed solution(compile from source) does not work using only 2008 Express editions. The C++ project will not compile as ATL is being removed from this version of Visual Studio. Also, one would need to compile the C++ part in Visual C++ Express and the C# part in Visual C# Express. As is, this program is useless to someone running x64 Windows and does not have a paid- for copy of Visual Studio. The proposed solution(compile from source) does not work using only 2008 Express editions. The C++ project will not compile as ATL is being removed from this version of Visual Studio. Also, one would need to compile the C++ part in Visual C++ Express and the C# part in Visual C# Express. As is, this program is useless to someone running x64 Windows and does not have a paid- for copy of Visual Studio. Jun 26, 2009 r285 ([No log message]) committed by staudenmeyer - [No log message] [No log message] May 21, 2009 r284 ([No log message]) committed by staudenmeyer - [No log message] [No log message] May 16, 2009 r282 (fixed deadlock problem, using GetThreadTimes to profile thre...) committed by staudenmeyer - fixed deadlock problem, using GetThreadTimes to profile thread time instead of wall time, always use 64 bit integers for FunctionIDs fixed deadlock problem, using GetThreadTimes to profile thread time instead of wall time, always use 64 bit integers for FunctionIDs May 15, 2009 r281 (added x64 support) committed by staudenmeyer - added x64 support added x64 support May 08, 2009 r280 (interface improvements) committed by staudenmeyer - interface improvements interface improvements May 05, 2009 r279 (larger profiling interval) committed by staudenmeyer - larger profiling interval larger profiling interval May 05, 2009 r278 ([No log message]) committed by staudenmeyer - [No log message] [No log message] Apr 23, 2009 issue 8 (Nprof doesn't work on Vista-64. ) commented on by scottp100 - Check out a threads on the subject: http://forums.xna.com/forums/p/9099/167831.aspx Check out a threads on the subject: http://forums.xna.com/forums/p/9099/167831.aspx Apr 23, 2009 issue 8 (Nprof doesn't work on Vista-64. ) reported by scottp100 - What steps will reproduce the problem? 1. Try running on Vista-64 2. Program crashes immediately (also it starts with big red x's in the interface. 3. What is the expected output? What do you see instead? See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************ Exception Text ********** System.BadImageFormatException: is not a valid Win32 application. (Exception from HRESULT: 0x800700C1) at DotNetLib.Windows.Forms.ContainerListView.DrawBorder(Graphics g) at DotNetLib.Windows.Forms.ContainerListView.OnPaint(PaintEventArgs e) at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer, Boolean disposeEventArgs) at System.Windows.Forms.Control.WmPaint(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at DotNetLib.Windows.Forms.ContainerListView.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ********** Loaded Assemblies ********** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000) CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll ---------------------------------------- NProf Assembly Version: 1.0.2483.29070 Win32 Version: 1.0.2483.29070 CodeBase: file:///C:/Program%20Files%20(x86)/NProf-0.10/NProf.exe ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- DotNetLib.Windows.Forms Assembly Version: 0.1.0.6 Win32 Version: 0.1.0.6 CodeBase: file:///C:/Program%20Files%20(x86)/NProf-0.10/DotNetLib.Windows.Forms.DLL ---------------------------------------- ********** JIT Debugging ********** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box. What version of the product are you using? On what operating system? vprof - v0.10 Please provide any additional information below. What steps will reproduce the problem? 1. Try running on Vista-64 2. Program crashes immediately (also it starts with big red x's in the interface. 3. What is the expected output? What do you see instead? See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ********** Exception Text ********** System.BadImageFormatException: is not a valid Win32 application. (Exception from HRESULT: 0x800700C1) at DotNetLib.Windows.Forms.ContainerListView.DrawBorder(Graphics g) at DotNetLib.Windows.Forms.ContainerListView.OnPaint(PaintEventArgs e) at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer, Boolean disposeEventArgs) at System.Windows.Forms.Control.WmPaint(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at DotNetLib.Windows.Forms.ContainerListView.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ********** Loaded Assemblies ********** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000) CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll ---------------------------------------- NProf Assembly Version: 1.0.2483.29070 Win32 Version: 1.0.2483.29070 CodeBase: file:///C:/Program%20Files%20(x86)/NProf-0.10/NProf.exe ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- DotNetLib.Windows.Forms Assembly Version: 0.1.0.6 Win32 Version: 0.1.0.6 CodeBase: file:///C:/Program%20Files%20(x86)/NProf-0.10/DotNetLib.Windows.Forms.DLL ---------------------------------------- ********** JIT Debugging ************ To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box. What version of the product are you using? On what operating system? vprof - v0.10 Please provide any additional information below. Jan 30, 2009 issue 3 (Generics) Owner changed by staudenmeyer - Owner: udaymshanbhag Owner: udaymshanbhag Jan 30, 2009 issue 5 (Inner classes in signatures) Owner changed by staudenmeyer - Owner: udaymshanbhag Owner: udaymshanbhag Jan 30, 2009 issue 7 (Start profiled app with specified working directory) Owner changed by staudenmeyer - Owner: udaymshanbhag Owner: udaymshanbhag Jan 30, 2009 issue 5 (Inner classes in signatures) Labels changed by staudenmeyer - Labels: Priority-Medium −Priority-Low Labels: Priority-Medium −Priority-Low Jan 30, 2009 issue 2 (Exclusive time) Labels changed by staudenmeyer - Labels: Priority-Medium −Priority-Low Labels: Priority-Medium −Priority-Low Jan 30, 2009 issue 3 (Generics) Labels changed by staudenmeyer - Labels: Priority-Medium −Priority-Low Labels: Priority-Medium −Priority-Low

issue 8 (Nprof doesn't work on Vista-64. ) reported by scottp100 - What steps will reproduce the problem? 1. Try running on Vista-64 2. Program crashes immediately (also it starts with big red x's in the interface. 3. What is the expected output? What do you see instead? See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.BadImageFormatException: is not a valid Win32 application. (Exception from HRESULT: 0x800700C1) at DotNetLib.Windows.Forms.ContainerListView.DrawBorder(Graphics g) at DotNetLib.Windows.Forms.ContainerListView.OnPaint(PaintEventArgs e) at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer, Boolean disposeEventArgs) at System.Windows.Forms.Control.WmPaint(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at DotNetLib.Windows.Forms.ContainerListView.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000) CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll ---------------------------------------- NProf Assembly Version: 1.0.2483.29070 Win32 Version: 1.0.2483.29070 CodeBase: file:///C:/Program%20Files%20(x86)/NProf-0.10/NProf.exe ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- DotNetLib.Windows.Forms Assembly Version: 0.1.0.6 Win32 Version: 0.1.0.6 CodeBase: file:///C:/Program%20Files%20(x86)/NProf-0.10/DotNetLib.Windows.Forms.DLL ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box. What version of the product are you using? On what operating system? vprof - v0.10 Please provide any additional information below.

What steps will reproduce the problem? 1. Try running on Vista-64 2. Program crashes immediately (also it starts with big red x's in the interface. 3. What is the expected output? What do you see instead? See the end of this message for details on invoking just-in-time (JIT) debugging instead of this dialog box. ************** Exception Text ************** System.BadImageFormatException: is not a valid Win32 application. (Exception from HRESULT: 0x800700C1) at DotNetLib.Windows.Forms.ContainerListView.DrawBorder(Graphics g) at DotNetLib.Windows.Forms.ContainerListView.OnPaint(PaintEventArgs e) at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer, Boolean disposeEventArgs) at System.Windows.Forms.Control.WmPaint(Message& m) at System.Windows.Forms.Control.WndProc(Message& m) at DotNetLib.Windows.Forms.ContainerListView.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam) ************** Loaded Assemblies ************** mscorlib Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000) CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v2.0.50727/mscorlib.dll ---------------------------------------- NProf Assembly Version: 1.0.2483.29070 Win32 Version: 1.0.2483.29070 CodeBase: file:///C:/Program%20Files%20(x86)/NProf-0.10/NProf.exe ---------------------------------------- System.Windows.Forms Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll ---------------------------------------- System Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll ---------------------------------------- System.Drawing Assembly Version: 2.0.0.0 Win32 Version: 2.0.50727.3053 (netfxsp.050727-3000) CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll ---------------------------------------- DotNetLib.Windows.Forms Assembly Version: 0.1.0.6 Win32 Version: 0.1.0.6 CodeBase: file:///C:/Program%20Files%20(x86)/NProf-0.10/DotNetLib.Windows.Forms.DLL ---------------------------------------- ************** JIT Debugging ************** To enable just-in-time (JIT) debugging, the .config file for this application or computer (machine.config) must have the jitDebugging value set in the system.windows.forms section. The application must also be compiled with debugging enabled. For example: <configuration> <system.windows.forms jitDebugging="true" /> </configuration> When JIT debugging is enabled, any unhandled exception will be sent to the JIT debugger registered on the computer rather than be handled by this dialog box. What version of the product are you using? On what operating system? vprof - v0.10 Please provide any additional information below.

Older