From: Vladimir Prus <vladimir@codesourcery.com>
To: gdb@sources.redhat.com
Subject: RE: Multiexec MI broke MI compatibility?
Date: Sat, 05 Jun 2010 05:16:00 -0000 [thread overview]
Message-ID: <hucmij$nmj$1@dough.gmane.org> (raw)
In-Reply-To: <F7CE05678329534C957159168FA70DEC53ACFAC64D@EUSAACMS0703.eamcs.ericsson.se>
Marc Khouzam wrote:
>
>
>> -----Original Message-----
>> From: Frederic Riss [mailto:frederic.riss@gmail.com]
>> Sent: Wednesday, April 14, 2010 4:12 AM
>> To: Marc Khouzam
>> Cc: Vladimir Prus; gdb@sources.redhat.com
>> Subject: Re: Multiexec MI broke MI compatibility?
>>
>> Hi!
>>
>> On 13 April 2010 22:33, Marc Khouzam
>> <marc.khouzam@ericsson.com> wrote:
>> >>> 797,748 10-list-thread-groups i1
>> >>> 797,748 10^error,msg="invalid group id 'i1'"
>> <-------------- when we ask for the same is, GDB rejects it
>> >>> 797,749 (gdb)
>> >>
>> >> This sounds like a bug indeed. Can you file an issue?
>> >
>> > I'm hoping Frederic can do that since he knows the proper details.
>>
>> Done here:
>> http://sourceware.org/bugzilla/show_bug.cgi?id=11499
>
> As there are discussions for an earlier release of 7.2,
> I wanted to mention this regression.
> I think this is something that should be fixed before 7.2.
Yes, working on that now.
>
>> This leaves the question of whether the thread-group-created
>> notification name change was appropriate (From a backward
>> compatibility POV, not from a pure 'it makes sense' angle).
>
> As for this, is the plan to keep the change or to revert?
The plan is to keep the change, sorry.
- Volodya
next prev parent reply other threads:[~2010-06-05 5:16 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
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 [this message]
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='hucmij$nmj$1@dough.gmane.org' \
--to=vladimir@codesourcery.com \
--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