When starting a remote debugging session I get the following error (about 4 times) right before the program breaks into main(): The debugger component encountered internal error while processing reply from gdb. Please submiit a bug report. The exception is: MI type error The MI response is: ^done,threads=[{id="1",target-id="Thread 1",details="CPU#0 [running]",frame={level="0",addr="0x0011099c",func="hydrax_init",args=[{name= "p_mboot",value="0x10000"},{name="initial_stack",value="524032"}],file="main.c", fullname="/home/fernan/Projects/hydrax/kernel/main.c",line="45"},state="stopped" }],current-thread-id="1" After I OK the error dialog things may seem fine except that breakpoints in some files don't work at all (I can set them but it never breaks). It happens every time but I don't see any obvious reason why it happens where it does. Breakpoints on the same files work fine when set from the gdb cli or another frontend (kdbg). It only happens with version 4.7.1, 4.6.0 and 4.7.0 (which was deleted) both work fine. I have tested and been able to reproduce with the latest stable gdb and all the unstables except 9999 (which I didn't test). Reproducible: Always Steps to Reproduce: 1.Setup a host to debug. I used QEMU with the built-in GDB stub. 2.Setup Remote Debugging on Kdevelop - My setup is pretty much the same as this: https://sites.google.com/site/embedded2009/weekly-small-project-list/use-kdevelop-to-develop-linux-kernel except I'm not debugging the Linux kernel and I'm using i386. 3.Press debug launch shortcut to start debuggig. Actual Results: Error dialog is shown and some breakpoints don't work. Expected Results: Everything works.
Created attachment 399704 [details] emerge --info
This was probably introduced here: http://quickgit.kde.org/?p=kdevelop.git&a=commit&h=7f5008b07506e6a4b0d817bf7735be4d19da8790 Perhaps one of these follow-up commits solves your issue? http://quickgit.kde.org/?p=kdevelop.git&a=commitdiff&h=0f6d8770f64bbdc6031db93d0eb27fee48fc5018 http://quickgit.kde.org/?p=kdevelop.git&a=commitdiff&h=66e3468d1191d2c63261e8d94d085335e5ab23ea
Thank you. Unfortunately, no dice. Both commits are already on 4.7.1
Created attachment 402360 [details, diff] gdb patch
Created attachment 402362 [details, diff] kdev-4.7.1-gdb.patch
Created attachment 402364 [details] kdevelop-4.7.1.ebuild
Well, you where right about the commit that introduced the bug. It looks like they're assuming that the "thread-group-started" message will always come as a response to a exec-run command. In my case it is being sent by gdb when the gdbinit file is loaded, so it's marking the last command as received and it gets out of sync with gdb. I uploaded a patch and an updated ebuild. I just went by their comment that seems to indicate that the message is only expected for the exec-run command and only set the flag when that's the current command. I'll file an upstream bug, in the meantime this fixes the problem. It probably should never be set there because -exec-run gives a ^running response?
https://bugs.kde.org/show_bug.cgi?id=346827
Thanks for the investigation. Hopefully we can get your patch integrated upstream, backport it, and finally get 4.7.1 stabilised.
Thank-you for reporting and following up. This is now fixed in CVS. + 03 Aug 2015; Michael Palimaka <kensington@gentoo.org> + +files/kdevelop-4.7.1-gdb.patch, +kdevelop-4.7.1-r1.ebuild: + Backport patch from upstream to solve remote debugging error wrt bug #544410.
