SOS!

[Aleix Pol]

On Mon, May 4, 2015 at 2:37 PM, Leon Pollak <leonp at plris.com> wrote:
> Hello, gurus.
>
> Recently I was stupid enough to update my FC20 to FC21.
> Since that, several things stop working, the worth is gdb under
> kdevelop (4.7.1).
>
> I am doing remote cross-debugging for arm with gdb-7.7 and also tried
> with gdb-7.5.50.
>
> Plane gdbs with the same gdbinit file work perfect.
>
> Under kdevelop, starting the debug session, I receive:
> The exception is: MI type error
> The MI response is: ^done,threads=[{id="2",target-id="Thread
> 880.881",frame={level="0",addr="0x400314bc",func="pthread_yield",args=[],from="/lib/libpthread.so.0"},state="stopped",core="0"},
> {id="1",target-id="Thread
> 880.880",frame={level="0",addr="0x000bff34",func="main",args=[{name="argc",value="1"},
> {name="argv",value="0xbeea2e84"}],file="/Projects/CSU/src/main.cpp",fullname="/Projects/CSU/src/main.cpp",line="47"},state="stopped",core="0"}],current-
> thread-id="1"
>
> Pressing OK, gives me my application waiting at the main.cpp BP.
> Stepping over works.
> Setting BP at 3 lines later current position already does not -
> application runs without BP.
>
> Running without BP at the beginning works, but there is no way to stop
> the running application - pressing stop does nothing.
> Exiting the debugger does not do a thing on the target.
>
> Any help/recommendation will be highly(!!!) appreciated.
> Even how to go back to the previous kdevelop version...
>
> Thanks!
> --
> Leon
> _______________________________________________
> KDevelop mailing list
> KDevelop at kde.org
> https://mail.kde.org/mailman/listinfo/kdevelop

Personally I have no idea of what can be going wrong, maybe you can
investigate whether there was a big change in gdb MI? I doubt though,
especially at 7.5...

Another possibility is that your gcc 5 is acting up? I've already seen
bug reports of weird things going on...

HTH,
Aleix

PS: CC'ing Nicolai who was the last to take a look at the codebase, AFAIR.