Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

1.3 Source Insight Configuration

    • Run for Source Insight.
  • Caution : You have to run Dexter Daemon first,  Do not use "Run as administrator".
    • Then Open "Base " Project as below:  (menu) > Project > Open Project... 
    Image Removed"C:\dexter_daemon_#.#.#_64\dexter.em" macro file had been added "Base" Project.  
    (Menu > Project >
    • Image Added

    • Click the right button of the mouse on a project window. And then Click "Add and Remove Project Files...
    )
    • "
      Image Added
    Put 
    • Put "dexter.em" file path on [File Name] label, and then click "Add" button.
    Image RemovedYou have to check Dexter
    • Image Added
      ※ If you have the dexter.em file
    has added in "Base" Project
    • that is already added in Base project, remove it.
      Image Added
    • Dexter.em file has added in Base project.
      Image Modified


    • It must check Event Handling option in Preferences.

    • (menu > Options > Preferences... > Tab of General  > Misc > check 'Enable event handlers' )
    Image Removed
    • Image Added


    • You have to restart to Source Insight. If you start Sourceinsight, the Dexter is will begin.


1.4 Run static analysis on Dexter Daemon

  • Open Project that you develop package in Source Insight : (Project > Open Project)
  • Open the file, and then edit and save a source code file.
  • After a while, static analysis result and log added in Dexter daemon.
  • Image RemovedImage Added
    • The Fist execution may take more time due to the necessary libraries to load the result.
    • After installing the SSD shows the results more quickly, But It take the some minute that you use the network drive.
  • When you are editing in the Source Insight, a static analysis results are displayed as a bookmark later.
    (By pressing the up and down keys, an event is generated to display bookmarks in Source Insight)
  • You can remove of defect refer to bookmark or defect description on Dexter daemon.
    (Dexter Daemon > click on the checker name  > click on the right mouse button  > click 'Checker Description'




  • Caution
    • When running a static analysis based on "FILE" option, defect may be detected smaller than "PROJECT" option. Because it run without related header file.
    • If you want to analysis the source code with header file, you need to add the Project information on Dexter Daemon.(refer as below "2.1 Run static analysis by project")

...

  • The static analysis is only check defect in file on Source Insight, but you can check all of defects in project scope through Dexter Daemon.
  • Purpose of use
    • You can check Source code and all of defects in Dexter WEB.
  • If you run analysis by this mode, defects are detected by "admin" in Dexter WEB.
    Image Added
  • Click "Run Dexter static analysis" Icon () to open configureation by project, module path, or files.
  • Set up project information through under the static analysis the dialog box. And then click OK button.
    ※Caution : Files under 2MB only are target to analize.

    • Project NamemandatoryProject name must be same to the Source Insight Project. (otherwise the results will not detected)
    • Project Home Directorymandatory. You need to include the 'top-level' directory related "package". ※ DO NO USE 'blank' , 'Korean' and 'Special Character' in the path.
    • Scopemandatory. Specify a range of static analysis
      • PROJECT: Run for Project scope. It can identify defects in Source Insight. But source code is not visible in Dexter WEB .
      • FOLDER: Run for FOLDER scope(Sub directory are automatically included)
      • SNAPSHOT: If you can check the "SNAPSHOT" option, this information can use weekly defect analysis. The source code can be show in Dexter WEB.
    • Source Directorymandatory. You need to include the 'top-level' directory that related source files.Sub directorys are automatically included
      • +/- button: Manually Save / Update .
      • auto: It is automatically add all of the directory with the name 'src', 'source'.
      • reset: Remove all List
    • Header Directoryoption: You need to include the 'top-level' directory that related header files.Sub directory are automatically included (C / C ++ Only)
      • auto: It is automatically add all of the directory with the name 'include', 'inc','i' .
      • You need to added another directory.
    • Target Directory: If you want to check for "Folder" Scope, you can use this option.
    • Configuration Listoption: When you save the current configuration,"Project name - Project folder is the save "Key".
      • After registration, you can re-use several additional configuration information. But only one registration per project.
      • + : Save / Update.
      • - : Remove.

...