Difference between revisions of "Programming Howto:Attach the Debugger to a BCI2000 Module"

From BCI2000 Wiki
Jump to: navigation, search
(Next step)
Line 1: Line 1:
Duplicate a SignalGenerator batch file from the BCI2000 batch directory that is similar to your needs
+
==Back==
 +
To [[Programming Howto:Building and Customizing BCI2000|this howto's overview page]].
 +
 
 +
==Create a batch file to start up your configuration==
 +
Duplicate a SignalGenerator batch file from the BCI2000 batch directory. Which one you choose may depend on the task your module is going to be used with.
  
 
[[File:debug_1.png]]
 
[[File:debug_1.png]]
  
Rename it to contain "VeryNiceSignalProcessing" in its name
+
Rename the duplicated file to contain "VeryNiceSignalProcessing" in its name.
  
 
[[File:debug_2.png]]
 
[[File:debug_2.png]]
  
Edit the batch file by adding <tt>--EvaluateTiming=0</tt> to the SignalGenerator line, and by replacing the signal processing module's name with "VeryNiceSignalProcessing"
+
Edit the batch file by adding <tt>--EvaluateTiming=0</tt> to the SignalGenerator line, and by replacing the signal processing module's name with "VeryNiceSignalProcessing".
  
 
[[File:debug_3.png]]
 
[[File:debug_3.png]]
  
Double-click the batch file to start up BCI2000
+
Double-click the batch file to start up BCI2000.
  
 
[[File:debug_4.png]]
 
[[File:debug_4.png]]
  
In the VisualStudio IDE, set a breakpoint in VeryNiceFilter::StartRun(), and choose "Attach to Process..." from the "Debug" menu
+
==Attach the debugger==
 +
In the VisualStudio IDE, set a breakpoint in <tt>VeryNiceFilter::StartRun()</tt>, and choose "Attach to Process..." from the "Debug" menu.
  
 
[[File:debug_5.png]]
 
[[File:debug_5.png]]
  
From the process list, choose "Very Nice Signal Processing", and click "Attach"
+
From the process list, choose "Very Nice Signal Processing", and click "Attach".
  
 +
==Verify that execution stops at the breakpoint==
 
[[File:debug_6.png]]
 
[[File:debug_6.png]]
  
Line 27: Line 33:
 
[[File:debug_7.png]]
 
[[File:debug_7.png]]
  
... and "Run", which will execute VeryNiceFilter::StartRun() ...
+
... and "Run", which will execute <tt>VeryNiceFilter::StartRun()</tt> ...
  
 
[[File:debug_8.png]]
 
[[File:debug_8.png]]
  
and cause the debugger to stop execution at the breakpoint you set earlier
+
and cause the debugger to stop execution at the breakpoint you set earlier.
  
 
[[File:debug_9.png]]
 
[[File:debug_9.png]]

Revision as of 15:09, 16 August 2018

Back

To this howto's overview page.

Create a batch file to start up your configuration

Duplicate a SignalGenerator batch file from the BCI2000 batch directory. Which one you choose may depend on the task your module is going to be used with.

Debug 1.png

Rename the duplicated file to contain "VeryNiceSignalProcessing" in its name.

Debug 2.png

Edit the batch file by adding --EvaluateTiming=0 to the SignalGenerator line, and by replacing the signal processing module's name with "VeryNiceSignalProcessing".

Debug 3.png

Double-click the batch file to start up BCI2000.

Debug 4.png

Attach the debugger

In the VisualStudio IDE, set a breakpoint in VeryNiceFilter::StartRun(), and choose "Attach to Process..." from the "Debug" menu.

Debug 5.png

From the process list, choose "Very Nice Signal Processing", and click "Attach".

Verify that execution stops at the breakpoint

Debug 6.png

In the Operator window, click "Set Config" ...

Debug 7.png

... and "Run", which will execute VeryNiceFilter::StartRun() ...

Debug 8.png

and cause the debugger to stop execution at the breakpoint you set earlier.

Debug 9.png

Next step

As a next step, learn how to programmatically wait for the debugger in a BCI2000 module.

See also

Programming Howto:Building and Customizing BCI2000