You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This ticket is more a question than a bug report, I'm not sure what I'm trying to do is actually supported, so please let me know.
Describe the bug
I'm trying to setup semihosting with cortex-debug, using J-Link.
I came accross the following page: https://mcuoneclipse.com/2023/10/14/semihosting-with-vs-code-on-rp2040/
In this page, the author uses a custom library, on my side I'm using standard newlib-nano.
I re-used the launch configuration shared in this page to enable semihosting, so I added this:
I don't see any printf output in the debug consol or in the "gdb-server" terminal.
But, in my workspace folder, I see files are created and contain the printf output, those files have somehow corrupted names, eg: :tt'$'\230\375\177
Also, I'm running gcov on the target, so when it dumps all the coverage results, the .gcda file name contains corrupted characters like the previous example.
I used Ozone to compare, and it correctly shows the printf/scanf in the terminal, and the .gcda file is named correctly.
Maybe worth to mention, I'm using VS Code in SSH from Windows to a Linux machine. The build/debug happens on the Linux machine.
Environment:
Cortex-Debug Version 1.12.1
OS: Linux Ubuntu 20.04 LTS
GDB Version: 10.2.90.20210621
Compiler Toolchain Version: GNU Arm Embedded Toolchain 10.3-2021.10
This ticket is more a question than a bug report, I'm not sure what I'm trying to do is actually supported, so please let me know.
Describe the bug
I'm trying to setup semihosting with cortex-debug, using J-Link.
I came accross the following page: https://mcuoneclipse.com/2023/10/14/semihosting-with-vs-code-on-rp2040/
In this page, the author uses a custom library, on my side I'm using standard newlib-nano.
I re-used the launch configuration shared in this page to enable semihosting, so I added this:
I don't see any printf output in the debug consol or in the "gdb-server" terminal.
But, in my workspace folder, I see files are created and contain the printf output, those files have somehow corrupted names, eg:
:tt'$'\230\375\177
Also, I'm running gcov on the target, so when it dumps all the coverage results, the .gcda file name contains corrupted characters like the previous example.
I used Ozone to compare, and it correctly shows the printf/scanf in the terminal, and the .gcda file is named correctly.
Maybe worth to mention, I'm using VS Code in SSH from Windows to a Linux machine. The build/debug happens on the Linux machine.
Environment:
launch.json
The text was updated successfully, but these errors were encountered: