Nytro Posted July 30, 2012 Report Posted July 30, 2012 [h=1]PEBrowseProfessional Interactive[/h] [h=2]Windows Debugger (Win32/Win64)[/h]PEBrowseDbg64 Interactive (v3.1) is a 64-bit executable and requires the .NET framework. It will debug Win32/Win64 executables, managed (.NET) and/or native. PEBrowse Professional Interactive (v9.3.3) is a debugger for Microsoft Windows 2000, Windows XP, Windows 2003, Windows Vista32, and Windows 7. PEBrowse Professional Interactive and PEBrowseDbg64 Interactive build upon the framework presented by PEBrowse Professional to create very powerful, versatile, and customizable Win32 and Win64 user mode debuggers/disassemblers, respectively. PEBrowse Interactive is not a source code debugger, but operates at the Intel x86 instruction level and therefore at the lowest level where your program executes. The debugger fully supports Microsoft .NET managed processes and seamlessly allows interop or mixed-mode debugging. PEBrowseDbg64 Interactive is an x64 native-code debugger that fully supports 32 and 64-bit .NET programs, includes using pre-JITted metadata to set breakpoints and steps through .NET thunks. PEBrowse Interactive can be set as the startup debugger using the system registry Image File Execution Options key - useful for debugging ASP.NET applications. There is a large array of breakpoint opportunities, including: [TABLE=class: pagetable, width: 95%] [TR] [TD=width: 33%] process initialization module load thread startup module exports [/TD] [TD=width: 33%] debug symbols JITted (Just-In-Time) methods user specified addresses [/TD] [TD=width: 34%] memory breakpoints conditional breakpoints one-time breakpoints [/TD] [/TR] [/TABLE]When a breakpoint fires or an exception in the process occurs, the interface provides easy access to full process context, including: [TABLE=class: pagetable, width: 95%] [TR] [TD=width: 33%] loaded modules valid memory ranges debug log messages register values (including debug, floating-point, and segment registers) stack addresses disassembly at the breakpoint or exception address [/TD] [TD=width: 33%] virtually unlimited numbers of disassembly and memory displays additional process information, including thread information kernel, USER32, GDI32 objects (32-bit only) critical sections process environment startup parameters [/TD] [TD=width: 34%] heap display (32-bit only) execution path summary subroutine discovery intermediate language disassembly (for .NET managed modules) [/TD] [/TR] [/TABLE]There are all of the usual debugging features, such as single-stepping, stepping into/over call statements, executing until a selected instruction, as well as running to the next branch instruction. You can even add breakpoints on a specific IL statement in a .NET managed method. Memory DWORD/QWORD displays automatically indicate if the value is a valid memory address in the context of the debugged process and these values whenever possible resolve to symbolic names or important process regions, e.g., thread stacks, process heaps, and module sections. The color-coded disassembly displays also attempt to use symbolic information as well as offering various highlighting options designed to allow easy analysis of the code. There is even convenient access to a scratchpad, a calculator, and tables for hex-to-ASCII values, common Win32 error codes (32-bit only), and Windows message codes (32-bit only). There are many more options available on each window by accessing the context-sensitive menu items (popups are present also). Screenshot PEBrowse Professional Interactive: Screenshot PEBrowseDbg64 Professional Interactive: Download PEBrowse Professional Interactive. Download PEBrowseDbg64 Interactive. Read the Tutorial. Sursa: Windows Debugger Quote
