From: Vladimir Prus <ghost@cs.msu.su>
To: gdb@sources.redhat.com
Subject: Re: Multiexec MI broke MI compatibility?
Date: Tue, 13 Apr 2010 16:54:00 -0000 [thread overview]
Message-ID: <hq27jo$g3a$1@dough.gmane.org> (raw)
In-Reply-To: <t2v87d3b2041004120629nde1ed98btdec46649d6206bb6@mail.gmail.com>
Frederic Riss wrote:
> 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),
This change was intended.
> the way to identify thread groups has changed
> (thus breaking the way Eclipse did that query)...
If the change from numeric ids to 'iNNN' broken anything, this is
DSF bug. The strings were *always* documented as opaque.
> All that changed
> with the introduction of Multiexec MI.
>
> This leads to some questions:
> - Was that expected?
The change from thread-group-created to thread-group-started was intended.
I don't think Marc raised any concerns about that. I was no aware that
any released DSF version has actual support for multiexec. I am not aware
of any other change from documentated behaviour.
> - What kind of backward compatibility does the MI interface provide?
It generally should be backward compatible within given MI version (currently 2).
> - Is there a GUI working with the latest GDB and supporting the
> Multiexec features?
No idea.
- Volodya
next prev parent reply other threads:[~2010-04-13 16:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-12 13:30 Frederic Riss
2010-04-13 16:54 ` Vladimir Prus [this message]
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='hq27jo$g3a$1@dough.gmane.org' \
--to=ghost@cs.msu.su \
--cc=gdb@sources.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