BugHunter Pro and the VeriLogger Simulators

4.2 Navigating Code with Buttons and Report Tabs

4.2 Navigating Code with Buttons and Report Tabs

Previous topic Next topic  

4.2 Navigating Code with Buttons and Report Tabs

Previous topic Next topic  

Several buttons on the main button bar are linked to the Editor Window code. The Error and Breakpoint tabs in the report window can also be used to open editor windows to associated sections of the source code.

Find previously viewed code with the File Location Buttons:

As you browse the source code by clicking in different editor windows, BugHunter remembers the places you have viewed.

Press the Next and Previous File Location buttons to hop between locations that you have viewed.

Find last executed line of code with the Goto Button:

During simulation, press the Goto Current Execution Statement button on the button bar to display the last  executed line of code in an editor window. This line will be marked with a similar yellow arrow symbol.

Find in Active Editor:

Click in an Editor window to make it the active editor.

Enter a string into the search box on the button bar.

Press the Find Next button to find the next instance of the search string in the active editor.

This is the same as using Editor > Find menu and F3 button to search again.

Find in Files menu searches through multiple files:

The Find in Files feature allows you to search through a specific directory, with or without its subdirectories, in search of a particular text string in a file. This feature can be used to search all files in the directory, or files with a particular file extension.

Select the Editor > Find in Files menu option to open the Find In Files dialog.

Fill out the dialog and press Find to perform the search.

The search results are displayed in the Report window Grep tab. Double-click on a row to open an editor showing the code.

 

Find Signal Declarations from the Drawing Window

In the Stimulus-and-Results diagram, right-click on a signal label and choose Go to Declaration to open an editor that displays the line of source code where the signal is declared.

Find Errors using the Report Window Error Tab:

The Errors tab in the Report window displays compilation errors. Double-click on an error to open an editor and display the line where the error was found.

Find Breakpoint locations using the Report Window Breakpoint Tab

The Breakpoints tab in the Report window displays all the breakpoints in the current project. Double-click on a breakpoint to open an editor and display the line where the breakpoint is located.