-
-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debug is broken with GDB 13 #546
Comments
Thanks for testing with a pre-release of GDB, it is really helpful to track down these problems before the full release of GDB. Where did you get your GDB 13 pre-release from? Does the problem also occur with GDB 12.1? The MI trace you have provided is showing an error in GDB itself, the Please let me know where you got GDB from, ideally including the commit it was built from, so we can identify how to formulate a bug report to GDB ahead of their release. |
It is the "Beta" version 12.2 of the ARM GNU Toolchain: https://developer.arm.com/downloads/-/arm-gnu-toolchain-downloads I tested with GDB 12.1.90, and the issue is not present. |
I can reproduce this error on Windows with the download you provided. It is fairly random, but occasionally CDT isn't receiving the sequence number back. This is either a GDB or CDT bug, not specifically embed-cdt, but I will persist here until we know where this bug properly belongs and can confirm it is resolved. |
I can reproduce this outside of CDT (notice the
When I run in the console I do see that GDB detects an exception condition (this is where it is detected) - I think that exception is because of EOF on input, but not sure. Regardless, the error seems to be on the read side, consider this where the
|
On some cursory additional testing it looking like LF line endings cause the problems, but CRLF does not. |
This sounds a lot like https://bugs.eclipse.org/bugs/show_bug.cgi?id=579687 - that was about Linux, but the workaround may be the same. cc: @Torbjorn-Svensson FYI |
I believe that this issue is indeed fixed in newer GDB as bminor/binutils-gdb@ac16b09 specifically talks about this issue being resolved. |
BTW the bug in GDB was introduced and fixed during the GDB 12 dev cycle. The fix is also part of the GDB 12.1 release in commit bminor/binutils-gdb@e312dfb Somewhat frustratingly, the 12.2.MPACBTI-Bet1 release is built from an older commit of GDB than 11.3.Rel1, even though the latter was released a month earlier. |
I submitted https://bugs.linaro.org/show_bug.cgi?id=5899 so that hopefully the Arm folk can build a new toolchain with a better version of GDB. |
Description
Debugging is not working with GDB 13 on Windows (not tested on other plateforms).
Steps to Reproduce
Expected behaviour: GBD Eclipse client is working like on the previous GDB versions (for example, there is no problem with GDB 10.1.90).
Actual behaviour: Eclipse is stuck on the "Configuring GDB..." step.
arm-none-eabi-gdb is indeed started with the usual command line (--interpreter=mi2 --nx).
the JLinkGDBServer is waiting for a TCP connection.
The gdb traces console shows this:
Nothing more happens. There is no CPU use at all, Eclipse is just waiting here. The GDB client will never connect to the GDB server, the program is not loaded / started.
However, the GDB arm-none-eabi-gdb client is actually working perfectly when using it from the command line.
Versions
Windows 10 20H2
ARM GCC Toolchain 12.2.MPACBTI-Bet1, including GDB 13.0.50
Eclipse 4.25.1.20220908-1200
Eclipse CDT C/C++ Development Tools Core 7.4.200.202205302218 org.eclipse.cdt.core
Eclipse CDT C/C++ Development Tools Core Native Utilities for Windows 6.0.300.202204200013 org.eclipse.cdt.core.win32
Eclipse CDT C/C++ Development Tools Core Native Utilities for Windows (x86_64) 6.0.700.202208222120 org.eclipse.cdt.core.win32.x86_64
Eclipse Embedded CDT Embedded C/C++ Debugging Core Plug-in 2.0.0.202208180721 org.eclipse.embedcdt.debug.core
Eclipse Embedded CDT Embedded C/C++ Debugging GDB Core Plug-in 5.2.0.202208180721 org.eclipse.embedcdt.debug.gdbjtag.core
Eclipse Embedded CDT Embedded C/C++ Debugging GDB UI Plug-in 5.1.1.202208180721 org.eclipse.embedcdt.debug.gdbjtag.ui
The text was updated successfully, but these errors were encountered: