Hey guys,
I just realized something. After reading Andrew's responses, as
well as some of the confusing documentation errors and bug reports
being posted on the GDB mailing list... Two things. First of all,
Andrew is definitely pulling annotate 2 out for the next release.
(Regardless of our concerns.)
SO... if GDB 5.4 comes out and MI is as buggy as we think it's going
to be, we should just detect the version of GDB in CGDB, and if the
version is 5.4 (or any buggy release), give the user an explanation
of why their GDB sucks, and that it's not our fault if they're
experiencing problems. That's the best I can come up with given how
inflexible Andrew is being, and the apparent instability of the
current MI interface.
I have personally given up on trying to talk to the GDB maintainers
in this regard. We should continue to go our own way and do what we
can to support the upcoming whacky releases of GDB.
Mike
|
