Difference between revisions of "Programming Howto:Programmatically wait for the Debugger in a BCI2000 Module"
|Line 3:||Line 3:|
In the <tt>VeryNiceFilter</tt> constructor, add a line with a <tt>SuggestDebugging</tt> statement, and rebuild.
In the <tt>VeryNiceFilter</tt> constructor, add a line with a <tt>SuggestDebugging</tt> statement, and rebuild .
Latest revision as of 13:30, 24 August 2018
In the VeryNiceFilter constructor, add a line with a SuggestDebugging statement, and rebuild in debug mode.
Double-click the "VeryNiceSignalProcessing" batch file you created earlier.
The VeryNiceFilter constructor is executed at module startup, so a "SuggestDebugging" dialog box will pop up immediately. The dialog box will stay in the front -- you may move it out of the way, but otherwise leave it alone.
Attach the debugger
In the VisualStudio IDE, choose "Attach to Process..." from the "Debug" menu.
Select the "Very Nice Signal Processing" process, click "Attach", and finally dismiss the "SuggestDebugging" dialog box by clicking "yes".
In the call stack, your own code will appear some frames below the top.
Double-clicking your own code's frame will take you to the location of the SuggestDebugging statement.
You may now step through the code, set breakpoints, etc. When you are done, don't forget to "Quit" the Operator module from its "File" menu to terminate any BCI2000 modules that are still running.
As a next step, learn how to deploy a release version of a BCI2000 module.