From: Frederic Riss <frederic.riss@gmail.com>
To: gdb@sourceware.org
Subject: Multiexec MI broke MI compatibility?
Date: Mon, 12 Apr 2010 13:30:00 -0000 [thread overview]
Message-ID: <t2v87d3b2041004120629nde1ed98btdec46649d6206bb6@mail.gmail.com> (raw)
Hi,
I tried to use the latest GDB CVS version with Eclipse Galileo DSF
Debug launch, and it failed to launch a debug session. I looked at the
differences with Fedora's GDB7.0 that works in the same environment
and found out that the way MI reports threads totally changed. Some
notifications have changed (eg. thread-group-created became
thread-group-started), the way to identify thread groups has changed
(thus breaking the way Eclipse did that query)... All that changed
with the introduction of Multiexec MI.
This leads to some questions:
- Was that expected?
- What kind of backward compatibility does the MI interface provide?
- Is there a GUI working with the latest GDB and supporting the
Multiexec features?
Thanks!
Fred
next reply other threads:[~2010-04-12 13:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 13:30 Frederic Riss [this message]
2010-04-13 16:54 ` Vladimir Prus
2010-04-13 17:32 ` Marc Khouzam
2010-04-13 19:40 ` Vladimir Prus
2010-04-13 20:33 ` Marc Khouzam
2010-04-14 8:12 ` Frederic Riss
2010-06-04 13:46 ` Marc Khouzam
2010-06-05 5:16 ` Vladimir Prus
2010-06-08 0:36 ` Marc Khouzam
2010-06-21 18:32 ` Marc Khouzam
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=t2v87d3b2041004120629nde1ed98btdec46649d6206bb6@mail.gmail.com \
--to=frederic.riss@gmail.com \
--cc=gdb@sourceware.org \
/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