Open PaulWessel opened 9 months ago
Got debugging started using the Run menu and "Start Debugging" and Step into/over selections. Used F10 and F11 once I changed keyboard setting to let these not start playing music... However, how do I inspect the value of a variable? Right-click no work, so how is it done in VSC? If similar to Windows then perhaps @joa-quim might be helpful here too?
Sorry, no idea. I use it as the Julia debugger where variables show on the left side pane. I guess that for C it should be somewhat similar but know no more. This typical of what I see from the Julia debugger.
I finally got that working too. But for a VSC rookie I think we need more info in the debugging section. Once Max and I wrap this up perhaps you could use that section for a Debugging GMT.jl with VSC since it is likely to be very similar.
Debugging .jl is trivial. What is really interesting is debugging the GMT C via GMT.jl
After extreme procrastination I am finally trying to set up debugging using Visual Studio Code. I have the latest version 1.85.1 (Universal). Some edits are needed in the description, I think.
GMT_Call_Module
near Line 112 is now presumably 122?If I click on the Problems menu button for the debug console it tells me it cannot find gdal.h? But build/gmt6/bin seems OK.
Finally tried a regular terminal window outside of VSC and prepended /Users/pwessel/UH/RESEARCH/CVSPROJECTS/GMTdev/gmt-dev/vbuild/gmt6/bin to my $PATH and set the
GMT_SESSION_NAME=vscodedebug parameter
. I then added that stop point at L122 and rungmt --help
. I expected to see VSC stop execution at line 122 but it just ran the whole command. Same if I opened a Terminal from VSC and set the same parameters before runninggmt plot
. Same result. So what am I missing? I think running a CLI command is simpler for me than to edit tasks.json all the time. With Xcode one must hook either python or julia to the process but here there is no such thing so how can VSC connect my gmt call via build to VSC stop points?OK stopping here because I am stuck.