The ultimate objective Ring 3 debuggers may compare favorably with  with Ollydbg, the Ring 0 debuggers may contend with with Softice

Downloads the address:

1.1 editions improvements:

1 supports in ollydbg run the trace track way.
2 chm form help handbook completes
3 chm form order reference manual completes
4 further improves software the stability
5 Syser Ring 3 debuggers issues
6 revised the first start speed slow question

The Syser Debugger function mainly develops to following several directions:

1. devotes into software explains the aspect most intrepid debugging tool. (Official edition is possible inside to inlay some popular shells peels off the shell function.)
2. reduces procedure development and the debugging cycle, causes the driver the debugging to step into to the original code level entire graph debugging time. (Mainly is includes based on the C language and C++ language application procedure and driver)
3. provides nimble and the formidable card connection. Provides the card automatic loading and the manual loading and so on the many kinds of way. As well as will provide the card SDK (graph contact surface connection later possibly provides through the COM form).

Syser Debugger is based on the X86 platform specially is Windows NT the Family development essence level entire graph contact surface debugger. The support assembler-level debugging and the original code level debugging.

Syser Debugger may debug the Windows application procedure as well as the Windows driver.

Syser Debugger is perfect unifies IDA Pro and Softice as well as the Ollydbg function, causes to operate more convenient is quick. The function is more formidable.

System requirements :

1. 586/100 above processors (586/300+ or higher recommended)
2. Operating system requirement Windows 2000, Window XP, Windows 2003 or renewal edition.
3. At least 256MB physics memory
4. At least 10MB free disk space
5. VGA reveals the card. (Resolution 640*480 at least 16bit (65536) color)
6. Mouse or compatible pointing device . (PS2 Mouse, USB Mouse, TouchPad, TrackPoint)

Procedure characteristic:

1. colored assemblies supports.
2. original codes levels debugging support grammar matches colors.
3. original codes levels debugging supports the original code and the assembly instruction folds the type to reflects.
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. entire mice operations support. (Is doing not have keyboard equipment situation to be allowed to use mouse to control all operations)
7. command compatible Softice
8. multi-languages supports, first floor entire unicode realization.
9. plugin mechanisms support.
10. multi-CPU support, supports Intel Hyper-Threaded processors.
11. supports starts script. (is similar to approves processing document)
12. supports cut the board function, in 3 ring copies data to 0 ring debuggers in.
13. may with the Softice peaceful coexistence. Softice starts.Syser after Syser also may unload. Even may debug softice.
14. PDB debugging code message comprehensive support.
15. automatic loading actuations program debuggings.
16. supports debuggings input the comment.
17. supports bookmarks function.
18. in the counter- assembly window support address navigation function, double strikes the fast browsing different function through the mouse.
19. original codes debuggings support fast variable examines, through moves the mouse may examine the variable type as well as the variable value to the variable name on.
20. Syser realized IDA and the Softice function perfect union.
21. supports addresses overlapping quotation demonstration.
22. supports data quotation tabulates.
23. supports TouchPad, the TrackPoint equipment high-level processing mode.
24. supports multi- data window.
25. supports the multi- codes window convenience assembly code the browsing.
26. supports ollydbg run the trace track way.
27. debuggings code messages automatic production and automatic loading is quick-witted. Omitted the softice original code debugging troublesome step. If you develop and debug the use identical machine. Does not change the original code in you saves directory under situation, you so long as translate in you may in the execution document the mouse right key, in right key menu. Center chooses with "Debug with the Syser" vegetable single item may enter our debugger carries on the original code level or assembler-level debugging.


Posted on 2005-08-20 10:36:50 by wuyanfeng
Hm, it's a kernel-mode debugger but still has a windows style GUI? That seems pretty interesting... one of the main gripes with SoftICE is problems with video driver support and such...
Posted on 2005-08-20 11:39:23 by f0dder
I guess I should sticky it so that more people get to see this thread.
Posted on 2005-08-20 22:12:30 by roticv
Hey,wuyanfeng Code Warrior.
your Syser Debugger can't pass an exception.

Posted on 2005-08-22 08:09:41 by dcskm4200
Try this one, hope it runs well
Posted on 2005-08-25 04:28:38 by killl
;@echo off
;goto make
.model flat, stdcall?
option casemap :none?
option prologue: none
option epilogue: none
include \masm32\include\
include \masm32\include\
include \masm32\include\

includelib \masm32\lib\user32.lib
includelib \masm32\lib\kernel32.lib
Message_0 db 'SEHTest', 0
Message_1 db 'Hello from an exception handler!', 0
Message_2 db 'After writing!', 0
Temp DWORD ?
assume FS:nothing
push offset SEH_ExceptionsHandler
push FS:[0]
mov FS:[0], esp ; SEH_ExceptionsHandler.
xor eax, eax
mov dword ptr , 1 ; made a seh? <<<====STOP HERE.
invoke MessageBox, 0, addr Message_2, addr Message_0, MB_OK
pop FS:[0]
pop eax
invoke ExitProcess, 0
SEH_ExceptionsHandler proc lpEXCEPTION_RECORD, lpERR, lpCONTEXT, lpDispacherContext
push ebp
mov ebp, esp
mov ecx, lpCONTEXT
mov eax, offset Temp
mov dword ptr , eax ; EAX.
invoke MessageBox, 0, addr Message_1, addr Message_0, MB_OK
xor eax, eax
mov esp, ebp
pop ebp
SEH_ExceptionsHandler endp

end Start

set name=seh_1

? ? \masm32\bin\ml /c /coff %name%.bat
? ? \masm32\bin\Link /subsystem:windows %name%.obj
? ?
? ? if exist *.bak del *.bak
? ? if exist *.obj del *.obj

the above code can't still be passed.

Posted on 2005-08-25 07:51:48 by dcskm4200