codelldb: Json parsing error when debugging rust

Typical russian shit attitude…

Ah, sorry folks! Last minute fixes and all that… Fixed in 1.8.1

You released version that makes work with your extension not possible.

This is not true. You can use this extension perfectly fine without the cargo launch feature. Just point "program" to your binary in the target folder. In fact, the only reason I added cargo launch was because of Rust unit tests, which generate randomized filenames for the output binary. Supporting the rest of cargo modes seemed like a small logical extension of the above.

But perhaps you are right: since so many users find this feature useful, it should be added to the regression test suite. I have not done this so far because tests involving VSCode UI will require significant extension of the testing infrastructure.

You’ve released soft that made working with projects that were using it impossible. Perhaps next time do more thorough testing. I don’t think is too much to ask?

I am sorry that my work is not up to your high standards!

Same here. Downgrading to 174. Suggestion for the creator, could you please a) Test it more thorough b) Stop auto-updating? I’ve spent couple of hours today after I’ve started VSCode and got message that this extension got updated. I didn’t ask for any update. And what happened? The update is buggy and I couldn’t work half a day. Congratulations…

@vadimcn Default is to auto update. At least in my version of VSCode which is 1.72. But seriously, I’m not going to discuss now auto vs not auto update. Yes, soft comes out with bugs, I understand that. But there are bugs and there are BUGS. You released version that makes work with your extension not possible. That is a BUG in my book, and I was suggesting bit more thorough testing. Yet, you started being very offensive and giving me attitude… Guy, I know that this is a free soft and everything, but some quality is expected even from free soft. Let me repeat: You’ve released soft that made working with projects that were using it impossible. Perhaps next time do more thorough testing. I don’t think is too much to ask?

@smallB007 I don’t control auto-updates, you do.

No I don’t. So perhaps next time you state something which is not correct ask?

@jaques-sam, you shouldn’t be running the binary, only building it using cargo. The output of the build is then launched by the debugger.

Some error in 1.9.2 for VS code. The “run” command will not be working and will cause this issue. After trying the “build” command, problem got solved. The command line arguments for the rust application should be configured in the outer args.

 {
            "type": "lldb",
            "request": "launch",
            "name": "Cargo launch",
            "cwd": "${workspaceFolder}/mg",
            "cargo": {
                "args": [
                    "build",
                    "--bin",
                    "execbin"
                   
                ]
            },
            "args": [

                "--model",
                "abc",
                "--locals",
                "aaa.yaml"
            ]
        }