From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: "'Tom Tromey'" <tromey@redhat.com>,
"'gdb-patches@sourceware.org'"
<gdb-patches@sourceware.org>
Subject: Re: [commit] [rfc] Print MI fullname even for non-existing files
Date: Thu, 03 Jan 2013 15:44:00 -0000 [thread overview]
Message-ID: <20130103154349.GA10450@host2.jankratochvil.net> (raw)
In-Reply-To: <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
next prev parent reply other threads:[~2013-01-03 15:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-17 15:59 Jan Kratochvil
2012-12-17 16:13 ` Andrew Burgess
2012-12-17 18:36 ` Jan Kratochvil
2012-12-17 16:33 ` Eli Zaretskii
2012-12-17 16:36 ` Jan Kratochvil
2012-12-17 18:33 ` Tom Tromey
2012-12-17 18:37 ` Jan Kratochvil
2012-12-17 18:41 ` Tom Tromey
2012-12-17 18:59 ` Jan Kratochvil
2012-12-28 0:17 ` Edjunior Barbosa Machado
2012-12-28 9:09 ` [commit] " Jan Kratochvil
2012-12-20 14:33 ` Marc Khouzam
2012-12-25 8:04 ` [commit] " Jan Kratochvil
2013-01-03 15:38 ` Marc Khouzam
2013-01-03 15:44 ` Jan Kratochvil [this message]
2013-01-03 16:04 ` Tom Tromey
2013-01-03 16:57 ` Joel Brobecker
2013-04-02 16:24 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130103154349.GA10450@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=tromey@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox