Don't add import section

[ohjeongwook]

No description provided.

[ohjeongwook]

srv2\binaries\10.0.00010240.00016384

• Name: __imp_SrvNetGetServerNameFlags

enum {
    CALL,       // 0: 
    CREF_FROM,  // 1:
    CREF_TO,    // 2: no
    DREF_FROM,  // 3: 
    DREF_TO,    // 4:
    CALLED      // 5: no
};

• ControlFlows: "4" (DREF_TO) "244344" "337286"
  1C003BA78 -> 1C0052586

.idata:00000001C003BA78                 extrn __imp_SrvNetGetServerNameFlags:qword

00000001C0052586 FF 15 EC 94 FE FF       call    cs:__imp_SrvNetGetServerNameFlags

• ControlFlows: "0" (CALL) "337240" "244344"
  1C0052558 -> 1C003BA78

00000001C0052558 41 0F B7 06             movzx   eax, word ptr [r14]
...
00000001C0052586 FF 15 EC 94 FE FF       call    cs:__imp_SrvNetGetServerNameFlags

• ControlFlows: "3" (DREF_FROM) "337286" "244344"

  1C0052586 -> 1C003BA78

00000001C0052586 FF 15 EC 94 FE FF       call    cs:__imp_SrvNetGetServerNameFlags

[ohjeongwook]

I found some issues introduced during refactoring of IDAAnalyzer::AnalyzeBlock with wrong basic block address.

5a27b8b

Except that, I think import section data can be beneficial in overall matching work. It has 0 length instruction hash, so it will not interfere with instruction hash match. It hash CALL/DREF_TO/DREF_FROM control flows and it might help in control flow match. We might want to exclude import function from showing in UI.