Open rvanlaar opened 4 years ago
You can add the support by changing the installed extension's package.json
. You would need to add a block such as:
"contributes": {
"languages": [{
"id": "yacc",
"extensions": [".yacc"],
"aliases": [ "YACC", "yacc" ]
}],
and then add in the breakpoint section:
"language": "yacc"
This will tell VSCode that breakpoints set in your file should go to our extension. If we get enough upvotes we can look at adding it as part of the official extension.
There should be a make
support issue already if you want to go upvote that one.
Hi @pieandcakes thank you for your response.
This is great. It works. One note: the extension for bison/yacc is .y.
The contributes part in the package.json looks like:
"contributes": {
"languages": [{
"id": "yacc",
"extensions": [".y"],
"aliases": [ "YACC", "yacc" ]
}],
I tried searching for a make
support issue, but couldn't find it.
If there is one that you know of, could you point me to it?
Integrated support for make
is something we've seen requested in our survey results, but I don't think an issue was ever opened on GitHub requesting this. If you wouldn't mind opening an issue for others to find and upvote, we would appreciate it.
Type: Debugger
Can't DEBUG YACC files.
I wrote a short yacc file which had a problem. I wasn't able to attach a debugger to the main function.
I would like to see the following:
Being able to set and hit breakpoints in the original .y file
Being able to hit breakpoints in the y.tab.c file (generated by yacc).
have automatic task support for makefiles (should this be a new issue)?
OS and Version: Ubuntu 19.10
VS Code Version: ms-vscode.cpptools
C/C++ Extension Version: 0.26.3
To Reproduce I made a short version of a yacc file to highlight the problems. This yacc file is not supposed to work, it's supposed to highlight the problems with the debugger. All the files are in this gist: https://gist.github.com/rvanlaar/000c06347ef6fd6bfb5e7ddb8e17f0aa
The y.tab.c is generated with debug options enabled:
yacc -t --debug --verbose hoc1.y
Steps to reproduce the behavior:
Additional context https://gist.github.com/rvanlaar/000c06347ef6fd6bfb5e7ddb8e17f0aa#file-full-debug-log If applicable, please include logging by adding "logging": { "engineLogging": true, "trace": true, "traceResponse": true } in your
launch.json
Add any other context about the problem here including log or error messages in your Debug Console or Output windows.