Behavior of Go To Definition

[lmapii]

Version: 1.66.2 (user setup)
Commit: dfd34e8260c270da74b5c2d86d61aee4b6d56977
Date: 2022-04-11T07:46:01.075Z
Electron: 17.2.0
Chromium: 98.0.4758.109
Node.js: 16.13.0
V8: 9.8.177.11-electron.0
OS: Windows_NT x64 10.0.19044

C/C++ v1.9.8

When using "Go To Definition" on #define macros the behavior seems to have changed: On macOS, this command always goes to the first expansion of the definition, i.e., to the actual definition. On windows, this now seems to jump to the full expansion in case of re-definitions without a parenthesis.

Consider the following:

module_a.h
    #define MODULE_A_SMTH 0x3
module_b.h
    #define MODULE_B_SMTH MODULE_A_SMTH
module_b.c
    uint8_t some_variable = MODULE_B_SMTH;

When using the context menu (or CTRL/ALT+click) on MODULE_B_SMTH within module_b.c, vscode now jumps to the definition of MODULE_A_SMTH instead of MODULE_B_SMTH.

I'd expect it to always go to the actual definition without expanding the macro - I can always continue navigating if it is not expanded. Added files and a screen recording.

Is there maybe some configuration option that has been added or am I missing something?

pkg.zip

c-demo-1650959996750.mp4

[lmapii]

Transferred to #9240.