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

From BCI2000 Wiki
Jump to: navigation, search
(Next step)
Line 36: Line 36:
  
 
==Next step==
 
==Next step==
As a next step, learn how to [[Programming Howto:Programmatically wait for the Debugger in a BCI2000 Module|Programmatically wait for the Debugger in a BCI2000 Module]].
+
As a next step, learn how to [[Programming Howto:Programmatically wait for the Debugger in a BCI2000 Module|programmatically wait for the debugger in a BCI2000 module]].
  
 
==See also==
 
==See also==

Revision as of 13:44, 16 August 2018

Duplicate a SignalGenerator batch file from the BCI2000 batch directory that is similar to your needs

Debug 1.png

Rename it 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

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"

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