This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [commit] [rfc] Print MI fullname even for non-existing files
- From: Jan Kratochvil <jan dot kratochvil at redhat dot com>
- To: Marc Khouzam <marc dot khouzam at ericsson dot com>
- Cc: "'Tom Tromey'" <tromey at redhat dot com>, "'gdb-patches at sourceware dot org'" <gdb-patches at sourceware dot org>
- Date: Thu, 3 Jan 2013 16:43:49 +0100
- Subject: Re: [commit] [rfc] Print MI fullname even for non-existing files
- References: <20121217155859.GA8029@host2.jankratochvil.net> <8738z4y1el.fsf@fleche.redhat.com> <E59706EF8DB1D147B15BECA3322E4BDC04CEB7@eusaamb103.ericsson.se> <20121225080350.GB11349@host2.jankratochvil.net> <E59706EF8DB1D147B15BECA3322E4BDC065997@eusaamb103.ericsson.se>
On Thu, 03 Jan 2013 16:38:04 +0100, Marc Khouzam wrote:
> > From: Jan Kratochvil [mailto:jan.kratochvil@redhat.com]
> > Besides that the compatibility of Eclipse <-> GDB across
> > versions is not too
> > great, FSF GDB HEAD fails with eclipse-cdt-8.0.1-4.fc16.x86_64:
> > Error in final launch sequence
> > Failed to execute MI command:
> > maintenance set python print-stack off
> > Error message from debugger back end:
> > Undefined maintenance set command: "python print-stack
> > off". Try "help maintenance set".
>
> This has been fixed in cdt-8.0.2:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=367788
This does not matter, the point was that GDB does not fully keep Front Ends
backward compatibility.
I remember some discussion around the deprecation so it was intentional.
Jan