Tuesday, July 24, 2007
Friday, July 13, 2007
Syser Debugger 1.92
Syser Debugger is designed for Windows NT Family based on X86 platform. It is a core-level debugger with full-graphical interfaces and supports assembly debugging and source code debugging.
Syser Debugger is able to debug Windows applications and Windows drivers.
Syser Debugger perfectly combines the functions of IDA Pro, Softice and Ollydbg, which makes operations easier and faster and provides powerful functions.
System requirements :
1. 586/100Hmz or higher processors (586/300Hmz+ recommended)
2. OS: Windows 2000, Windows XP, Windows 2003 or later.
3. At least 256MB RAM
4. At least 5MB free disk space
5. VGA Video Card(Resolution: 640*480, at least 16bit (65536) color)
6. Mouse or compatible pointing devices (PS2 Mouse, USB Mouse, TouchPad, TrackPoint).
Procedure Features:
1. Supports color disassembly.
2. Source code debugging supports syntax coloring.
3. Source code debugging supports collapsing mapping between source code and assembly instructions.
4. Supports dynamic loading and unloading.
5. entire keyboards operations support. (If is doing not have mouse equipment situation all operations all to be allowed to use keyboard to operate)
6. Full mouse action support (if no keyboard is available, all operations can be performed through mouse commands).
7. Commands are Softice-compatible
8. Multi-language support, fully implemented unicode at low level.
9. Supports plug-ins.
10. Supports multi-CPU and Intel Hyper-Threaded processors.
11. Supports startup scripts (similar to batch files).
12. Supports clipboard function, able to copy data from Ring 3 debugger to Ring 0 debugger.
13. Fully supports PDB debugging symbol files.
14. Automatically load drivers to debug.
15. Supports comments adding when debugging.
16. Supports bookmark function.
17. Address navigation is supported in disassembly windows and users can browse different functions quickly by double-clicking.
18. Source code debugging supports quick view of variables and users can view variable types and values by moving cursor over variable names.
19. Syser is the perfect combination of IDA and Softice functions.
20. Supports address cross-reference lists.
21. Supports data reference lists.
22. Supports the advanced processing modes of pointing devices, such as TouchPad, TrackPoint.
23. Supports multiple data windows.
24. Supports multiple code windows to facilitate the browsing of assembly code.
25. Supports run trace mode for ollydbg.
26. The automatic generation and automatic loading of debugging symbol files makes the complex procedure of source code debugging unnecessary. If you are developing and debugging on the same machine and the storage directory of the source code keeps unchanged, you could enter our debugger for source code debugging and assembly debugging simply by right-clicking the executable file you compiled and selecting Debug with Syser from the popup menu.

links:
http://rapidshare.com/files/42710591/SyserCommand.chm
http://rapidshare.com/files/42710597/DebuggerHelp.chm
http://rapidshare.com/files/42710603/download.php
after download rename to *.exe
Monday, June 18, 2007
Syser Debugger 1.91 Release
2. Fixed some bugs of sysboot.sys.
3. Enhanced i3here command, support drv parameter.
4. Enhanced bpx,bpm command, support IF and DO syntax.
5. Enhanced tss command,display more details.
Tuesday, June 12, 2007
Syser 1.9
| 1. | Supports multi-CPU and Intel Hyper-Threaded processors |
| 2. | Support Microsoft Windows 2000, Windows xp,Windows 2003 or Windows Vista operation system |
| 3. | Support VMWare and Virtual PC |
| 4. | Source code debugging supports syntax coloring. |
| 5. | Supports color disassembly |
| 6. | Commands are Softice-compatible |
EDB Linux Debugger 0.8.12
EDB Linux Debugger 0.8.12 Release
I do a lot of work analyzing applications which I do not have the source code for. On Windows, OllyDbg is the tool of choice, but there is no Linux (or any other *nix equivalent) that I could find. Sure we have GDB, but GDB and all it’s various frontends tend to lean towards debugging applications to which we have the source. What I really want is a debugger which is as functional and useable as OllyDbg but for Linux (and possibly more). So I started my own debugger based on the ptrace API in Linux, and it is coming along very nicely. The hex dump views are based on the QHexView I developed which gives things a very polished look.
I am happy to announce that version 0.8.12 of EDB is available under the GPL-2 license for download! Please give it a try and let me know what I can do to improve it. Documentation is pretty much non-existant, but that’s one of the reasons why this is not a 1.0 release :). Remember to read the README file, it has a lot of information, and please check the TODO list before asking about a missing feature, it may already be in the works. Enjoy!
EDB’s source tree contains a copy of the libdisasm since that it what it uses to perform dissassembly. libdisasm.a is already compiled in this directory and the source is configured to link against it statically, until having libdisasm.so present in /usr/lib/ is common on most distributions (I don’t have a gentoo ebuild yet :-P), I think this is the best way to address this.
Launch and attach to new process
View/Dump memory regions
Toggle execution breakpoints
The usual debug ops (step-into/step-over/run/break)
Effective address inspection
String searching (like strings command in *nix)
Debugging core is implemented as a plugin (using the QPlugin API) so people can have drop in replacements. Of course if a given platform has several debugging APIs available, then you may have a plugin that implements any of them.
Opcode search engine plugin has basic functionality (similar to msfelfscan/msfpescan
Debugging events are trapped in a seperate thread so as to not lock up the GUI
The data dump view is tabbed, allowing you to have several views of memory open at the same time and quickly switch between them.
Basic Heap analysis (lists busy/free blocks)
Importing of symbol maps
Byte pattern searching
One of the main goals of this debugger is isolation of the debugger core from the display you see. The interface is written in QT4 and thus source portable to many platforms. The debugger core is actually a plugin and the platform specific code is isolated to just a few files, porting to a new OS would require porting these few files and implementing a plugin which implements the “DebuggerCoreInterface” interface. Also, because the plugins are based on the QPlugin API, and do their work through the DebuggerCoreInterface object, they are almost always portable with just a simple recompile. So far, the only plugin I have written which would not port with just a recompile is the heap analysis plugin, due to it’s highly system specific nature.
0.8.12 released, adding a few fixes, a few speedups, and a few new features
CHANGELOG:
2007-02-26
———-
* Added ability to change the working directory opened applications run in.
2007-02-23
———-
* Improved about dialog box
2007-02-15
———-
* Added ability to dump the contents of a data view tab to a file.
2007-01-17
———-
* Added recent file list to File menu.
2007-01-16
———-
* Cleared internal state tracking on detach, nothing major.
2006-12-23
———-
* Added new stylized register view window, still working out the programmers API
for it, but at least it looks nice
link:
http://www.codef00.com/projects/debugger-0.8.12.tgz