In debug-macros:
When you use __system1(), __system2(), __system3() calls, argument variables like $PROJ_DIR$, $TARGET_DIR$, ect. are generally expanded and working when debugging in IAR Workbench.
However when debugging in VSCode, most of these arguement variables are not yet supported.
The below test script shows which ones are working in IAR EW and VSCode.
Currently in VSCode only the following are working:
$CONFIG_NAME$, $PROJ_DIR$, $PROJ_FNAME$, $TOOLKIT_DIR$.
All of the argument variables should be expanded, except a few which are known to not work in debug-mode.
The calls made with __system1/2/3 should work because variables (paths) are expanded properly.
Here is debug-log output when run in IAR (working, except those which are known to NOT work in debug-mode):
NOTE: if you see line with just the $VAR_NAME$ as output in one line, you know it could not be evaluated.
Some are expected to fail in debug-mode, IGNORE THOSE:
$COMPILER_ARGS$, $CUR_LINE$, $FILE_BNAME$, $FILE_BPATH$, $FILE_DIR$, $FILE_FNAME$, $FILE_PATH$.
...
Thu Nov 23, 2023 10:31:08: : $COMPILER_ARGS$
Thu Nov 23, 2023 10:31:08: : --> Output: COMPILER_ARGS: $COMPILER_ARGS$
Thu Nov 23, 2023 10:31:08: : --> Output: CONFIG_NAME: RAILCON
Thu Nov 23, 2023 10:31:08: : --> Output: CUR_DIR: D:\DEV\qcc710-fw-2.0\SES
Thu Nov 23, 2023 10:31:08: : $CUR_LINE$
Thu Nov 23, 2023 10:31:08: : --> Output: CUR_LINE: $CUR_LINE$
Thu Nov 23, 2023 10:31:08: : --> Output: DATE: 23/11/2023
Thu Nov 23, 2023 10:31:08: : --> Output: EW_DIR: "C:\Program Files\IAR Systems\Embedded Workbench 9.2"
Thu Nov 23, 2023 10:31:08: : --> Output: EXE_DIR: D:\DEV\qcc710-fw-2.0\SES\RAILCON\Exe
Thu Nov 23, 2023 10:31:08: : $FILE_BNAME$
Thu Nov 23, 2023 10:31:08: : --> Output: FILE_BNAME: $FILE_BNAME$
Thu Nov 23, 2023 10:31:08: : $FILE_BPATH$
Thu Nov 23, 2023 10:31:08: : --> Output: FILE_BPATH: $FILE_BPATH$
Thu Nov 23, 2023 10:31:08: : $FILE_DIR$
Thu Nov 23, 2023 10:31:08: : --> Output: FILE_DIR: $FILE_DIR$
Thu Nov 23, 2023 10:31:08: : $FILE_FNAME$
Thu Nov 23, 2023 10:31:08: : --> Output: FILE_FNAME: $FILE_FNAME$
Thu Nov 23, 2023 10:31:08: : $FILE_PATH$
Thu Nov 23, 2023 10:31:08: : --> Output: FILE_PATH: $FILE_PATH$
Thu Nov 23, 2023 10:31:08: : --> Output: LIST_DIR: D:\DEV\qcc710-fw-2.0\SES\RAILCON\List
Thu Nov 23, 2023 10:31:08: : --> Output: OBJ_DIR: D:\DEV\qcc710-fw-2.0\SES\RAILCON\Obj
Thu Nov 23, 2023 10:31:08: : --> Output: PROJ_DIR: D:\DEV\qcc710-fw-2.0\SES
Thu Nov 23, 2023 10:31:08: : --> Output: PROJ_FNAME: QCC_710_SES
Thu Nov 23, 2023 10:31:08: : --> Output: PROJ_PATH: D:\DEV\qcc710-fw-2.0\SES\QCC_710_SES.ewp
Thu Nov 23, 2023 10:31:08: : --> Output: TARGET_DIR: D:\DEV\qcc710-fw-2.0\SES\RAILCON\Exe
Thu Nov 23, 2023 10:31:08: : --> Output: TARGET_BNAME: QCC_710_SES
Thu Nov 23, 2023 10:31:08: : --> Output: TARGET_BPATH: D:\DEV\qcc710-fw-2.0\SES\RAILCON\Exe\QCC_710_SES
Thu Nov 23, 2023 10:31:08: : --> Output: TARGET_FNAME: QCC_710_SES.out
Thu Nov 23, 2023 10:31:08: : --> Output: TARGET_PATH: D:\DEV\qcc710-fw-2.0\SES\RAILCON\Exe\QCC_710_SES.out
Thu Nov 23, 2023 10:31:08: : --> Output: TOOLKIT_DIR: "C:\Program Files\IAR Systems\Embedded Workbench 9.2\arm"
Thu Nov 23, 2023 10:31:08: : --> Output: USER_NAME: frc
Thu Nov 23, 2023 10:31:08: : --> Output: WS_DIR: D:\DEV\qcc710-fw-2.0\SES
...
Actual behavior:
Here is debug-log output when run in VS-Code (buggy - does not expand most of the variables):
NOTE: if you see line with just the $VAR_NAME$ as output in one line, you know it could not be evaluated.
You will notice that almost all variables could not be evaluated/expanded.
Only the following are working in VSCode: $CONFIG_NAME$, $PROJ_DIR$, $PROJ_FNAME$, $TOOLKIT_DIR$.
Describe the bug:
In debug-macros: When you use
__system1(), __system2(), __system3()
calls, argument variables like$PROJ_DIR$, $TARGET_DIR$
, ect. are generally expanded and working when debugging in IAR Workbench. However when debugging in VSCode, most of these arguement variables are not yet supported.The below test script shows which ones are working in IAR EW and VSCode.
Currently in VSCode only the following are working:
$CONFIG_NAME$, $PROJ_DIR$, $PROJ_FNAME$, $TOOLKIT_DIR$.
To Reproduce:
Expected behavior:
All of the argument variables should be expanded, except a few which are known to not work in debug-mode. The calls made with
__system1/2/3
should work because variables (paths) are expanded properly.Here is debug-log output when run in IAR (working, except those which are known to NOT work in debug-mode):
NOTE: if you see line with just the
$VAR_NAME$
as output in one line, you know it could not be evaluated. Some are expected to fail in debug-mode, IGNORE THOSE:$COMPILER_ARGS$, $CUR_LINE$, $FILE_BNAME$, $FILE_BPATH$, $FILE_DIR$, $FILE_FNAME$, $FILE_PATH$
.Actual behavior:
Here is debug-log output when run in VS-Code (buggy - does not expand most of the variables):
NOTE: if you see line with just the
$VAR_NAME$
as output in one line, you know it could not be evaluated. You will notice that almost all variables could not be evaluated/expanded. Only the following are working in VSCode:$CONFIG_NAME$, $PROJ_DIR$, $PROJ_FNAME$, $TOOLKIT_DIR$
.Environment: