This shows you the differences between two versions of the page.
|
34s:howto_build_emulator [2011/10/31 10:22] mvcube Updated the section about debugging. |
34s:howto_build_emulator [2011/10/31 16:12] (current) mvcube Added instructions for the Debug compile |
||
|---|---|---|---|
| Line 29: | Line 29: | ||
| === Debugging === | === Debugging === | ||
| - | Pretty much any changes you make to the code should be done on the emulator first. | + | Pretty much any changes you make to the code should be done on the emulator first. You should build the debug version of the software. Just select "Debug" from the drop down menu and hit F7 to start the build. |
| - | By default, if you start Debugging from the windows GUI you will get the windows calculator. Debugging in Visual Studio works pretty much like any other GUI debugger - set breakpoints, step in, around and out etc... Hover the pointer over a variable usually displays it's current value. | + | By default, if you start Debugging from the Windows GUI you will get the Windows calculator. Debugging in Visual Studio works pretty much like any other GUI debugger - set breakpoints, step in, around and out etc... Hover the pointer over a variable usually displays it's current value. |
| To debug the original "curses" text emulator start wp34s_d.exe and select "Attach debugger..." from the Debug menu. Pick out your wp34s process from the list and click on "Attach". This has it's advantages in that it shows all registers, modes and stack values, but you need the "layout" file to know which keyboard key maps to which calculator key. | To debug the original "curses" text emulator start wp34s_d.exe and select "Attach debugger..." from the Debug menu. Pick out your wp34s process from the list and click on "Attach". This has it's advantages in that it shows all registers, modes and stack values, but you need the "layout" file to know which keyboard key maps to which calculator key. | ||