nflow | proven solution for orchestrating business processes | BPM library

There is one thing you can try: change the value of "cwd"(current working directory) in "launch.json" to the folder where you have your file to read. For example, if you have your file to read in the path "C:\Users\username\Documents\file.txt", just put the "cwd": "C:\Users\username\Documents", then compile and run it again.

The "launch.json" file controls the arguments for your C++ debugger and you can find a full list of such arguments including "cwd" in the reference of VS code here. One possible reason why you cannot read the file is that your program cannot find the file because your file is not in the search path of your program.

I had the same issue just now and tried to solve it by setting the current working directory although I'm not sure if that's the best way to do it. A better way is probably to run debugger with argument to add new directory to the search path(like what you can do in "task.json" using -I argument). I was not able to find an argument for gdb. But one thing is for sure: you have to let the program or debugger find the file in some way.

There are many issues with your current model. Here is a fix for your variable declaration and objective function that is easier to configure and read.