在早期版本的IDA中可以直接通过进程选项来设置Windbg的路径，但是在6.0之后这个菜单没了。

但是可以直接编辑ida.cfg文件来设置调试器路径，修改如下内容即可。

//-------------------------------------------------------------------------
//      Processor specific parameters
//-------------------------------------------------------------------------
#ifdef __PC__                           // INTEL 80x86 PROCESSORS
//
// Location of Microsoft Debugging Engine Library (dbgeng.dll)
// This value is used by both the windmp (dump file loader) and the windbg
// debugger module. Please also refer to dbg_windbg.cfg
// (note: make sure there is a semicolon at the end)

//DBGTOOLS = "C:\\Program Files\\Debugging Tools for Windows (x86)\\";将这一行注释修改为windbg的路径
DBGTOOLS = "C:\\WinDDK\\7600.16385.1\\Debuggers\\";

USE_FPP = YES // Floating Point Processor
// instructions are enabled

// IBM PC specific analyzer options

PC_ANALYZE_PUSH = YES // Convert immediate operand of "push" to offset
//
// In sequence
//
// push seg
// push num
//

Comment Viewer is a plug-in for Interactive Dissasembler (IDA) whose purpose is to provide an easy way for the security researcher to manage the comments in the database. It should prove to be useful on large analysis of binary code projects where keeping a good image of the executable actions is needed.

 The plug-in supports a variety of options to be as efficient as possible in a variety of cases, while keeping much of its simplicity. For more information on the various options, what they mean and how to use them please read the attached pdf

Orginal Download link:http://www.openrce.org/downloads/details/237/Comment_Viewer

Dbank Download link:http://dl.dbank.com/c0qtmkuof4

#include "idc.idc"

static ElementExist(arrayid,size,val)
{
  auto i,v;
  for(i=0;i

	

IDA Pro Advanced Edition v6.1 the multi processor, multi operating system, interactive disassembler is used by security professionals to build a safer internet; by governmental agencies to validate commercial software; by open-source activists to support undocumented architectures; by device driver developers to tackle complex compatibility issues; and by embedded developers to build a better future.