This is the mail archive of the
mailing list for the GDB project.
RE: MI non-stop interface details
- From: "Marc Khouzam" <marc dot khouzam at ericsson dot com>
- To: "Vladimir Prus" <vladimir at codesourcery dot com>
- Cc: "Pedro Alves" <pedro at codesourcery dot com>, <gdb at sourceware dot org>, "Pawel Piech" <pawel dot piech at windriver dot com>
- Date: Wed, 30 Apr 2008 10:22:51 -0400
- Subject: RE: MI non-stop interface details
> > I'm also leaning towards this: -exec-continue only continuing
> > the current thread, a la java.
> > Although, also having a 'continue all' may prove useful.
> Again -- exec-continue resuming just one thread will be a change in behaviour.
> We can take two approaches:
> 1. The MI interface we've discussed for non-stop is essentially MI3 (and will
> be used both in all-stop and non-stop mode). We're in position to change anything
> we like, and are not bound by backward compatibility, or anything.
> 2. The MI interface for non-stop is MI2 + minimal set of changes. I think that
> Pawel's opposition to the --thread idea indicates that he prefers this approach.
> Then, we rather not change the behaviour of existing commands.
> There are not many high-level warts in MI2/non-stop/async, so I'm willing
> to go with (2).
Yeah, I see that the less impactful is (2). Ok with me.