Skip to content

Updates and clarifications to Debugging GMT on macOS with Visual Studio #8258

Open
@PaulWessel

Description

@PaulWessel

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.

  1. Of course, the reference to the GMT_Call_Module near Line 112 is now presumably 122?
  2. OSX_DEPLOYMENT_TARGET could stay but might as well be updated to 14.0.
  3. Regarding "Click on the debug panel". I think this is called Debug Console now. Should we update Panel to Console throughout?
  4. Select gmt.begin from the debug drop-down menu. What dropdown menu? I've looked around and nothing obvious shows up. No green arrow to click either. Tell me how and I may add a picture to make this clear. Here is what I see and no obvious dropdown menu related to the Debug Console at the bottom:
vs

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 run gmt --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 running gmt 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.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions