Open KarimAshraf1995 opened 1 year ago
Hi @KarimAshraf1995.
Let's use this issue as a feature request to add linker errors to the gcc problem matcher.
Note that the gcc problem matcher is defined in full in our extension's package.json, currently as:
{
"name": "gcc",
"source": "gcc",
"owner": "cpptools",
"fileLocation": [
"autoDetect",
"${cwd}"
],
"pattern": {
"regexp": "^(.*?):(\\d+):(\\d*):?\\s+(?:fatal\\s+)?(warning|error):\\s+(.*)$",
"file": 1,
"line": 2,
"column": 3,
"severity": 4,
"message": 5
}
},
This feature request is being closed due to insufficient upvotes. Please leave a 👍-upvote or 👎-downvote reaction on the issue to help us prioritize it. When enough upvotes are received, this issue will be eligible for our backlog.
This feature request has received enough votes to be added to our backlog.
Environment:
Bug Summary:
$gcc problem matcher does not match linker errors. Trying to compile the example using standard g++ with -g flag will result in linker error with file and line info which should be matched.
To reproduce:
tasks.json
main.cpp
The output of the task when I run it on my machine is /tmp/ccghmjfX.o: In function `main': /home/karim/test/main.cpp:5: undefined reference to `external_func()' collect2: error: ld returned 1 exit status
Expected behavior:
Linker error should be matched in the problems panel and highlighted in source file at line 5