"Interrupt failed" occurred when using GDB OpenOCD Debugging about eclipse-plugins HOT 5 CLOSED

This is the log in the. metadata folder when the error occurs.

!ENTRY org.eclipse.cdt.dsf 4 10005 2023-12-29 16:03:28.006
!MESSAGE Request for monitor: 'RequestMonitor (org.eclipse.cdt.dsf.debug.ui.actions.DsfSuspendCommand$4$1@6979e769): Status ERROR: org.eclipse.cdt.dsf.gdb code=10004 Interrupt failed.' resulted in an error.
!SUBENTRY 1 org.eclipse.cdt.dsf.gdb 4 10004 2023-12-29 16:03:28.006
!MESSAGE Interrupt failed.

From the debug console, it can be seen that GDB did not receive any signal, and there was no response when I manually entered "interrupt" or CTRL+C in the debug console.

from eclipse-plugins.

This is the version information of the GDB I am using.

$ riscv32-elf-gdb --version
GNU gdb (2023-06-30_riscv32-elf-298a5116d25) 8.2.50.20190522-git
Copyright (C) 2019 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

from eclipse-plugins.

Please provide a detailed way to reproduce the issue, using the latest Eclipse, the latest xPack RISC-V GCC toolchain and the latest xPack OpenOCD.

from eclipse-plugins.

@ilg-ul Thanks!

Steps to Reproduce

1. Import a RISC-V C Project.
2. Click the "Debug Configurations" and create a new GDB OpenOCD Debugging.
3. Configure openocd and gdb.
4. Start debugging and "Continue".
5. Press button "Suspend".

When I use the official riscv-none-elf-gdb (xPack), this issue will not occur. So the problem may be that my GDB did not receive an interrupt signal. So could you please tell me how embedded cdt sends an interrupt signal to gdb in Windows? I want to investigate why my gdb cannot receive the signal.

Thank you for any reply!

from eclipse-plugins.

If you use GDB standalone without any Eclipse/CDT/Embedded CDT support then does Ctrl-C to break into the running program always work OK?

In the scenario that you originally outlined, does increasing the GDB remote timeout before attempting to suspend make any difference? E.g. set remotetimeout 10.

• https://sourceware.org/gdb/current/onlinedocs/gdb.html/Remote-Configuration.html

It might make sense to collect and upload a verbose OpenOCD (openocd -d3) and GDB traces logs for the issue in case they shed any light on what's going on/wrong here.

from eclipse-plugins.