![]() |
|
|
|
#1
|
|||
|
|||
|
windbg (or kd--console version) is pretty good imo, especially if you use livekd. The notable advantage is wndbg's native support of M$ symbols, therefore making it so much easier for kernel debugging. kd has some really good commands that makes it very easy to explore windows internals, data structures, functions, exports, etc. And they are free!
If you cannot afford softice, livekd+wndbg is the way to go for kernel level debugging. for ring3 debugging, olly is very good. |
|
#2
|
|||
|
|||
|
general speeking...
windbg is a weight-level tools,howbeit softice light-level.. all i say here suited for souce code debug,not disassemble. 1.load times when use symbols,windbg spilt every file into single .pdb file but sice pack all file into one .sym file. so,,when u debug a large project,sice will spend many time to load symbles file(in our project,it's 5 mins.) 2.c/s debug c/s debug is used in many kernel debug,(via COM1 or 1394) when remote debugger is enabled,sice is very fast than windbg. becauze windbg will spend time to detect symbols file and more work, which can be saw in win2k leaked code dir,\private\windbg64\... 3.expand funcs we can easy expand windbg funcs by design some plug-in tools, but iceext is only chocie of u. so,my advice... when debugged in small project,sice is first choice. |
![]() |
| Thread Tools | |
| Display Modes | |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Microsoft Detours Pro v3.0 | b30wulf | Source Code | 38 | 06-22-2018 10:41 |
| All Editions Win ISO from Microsoft | xsdenied07 | General Discussion | 12 | 04-19-2017 14:36 |
| microsoft ddk | kP^ | General Discussion | 3 | 10-20-2003 20:39 |