avoid -break-list calls
Niko Sams
niko.sams at gmail.com
Sat Jun 27 09:56:13 UTC 2009
On Sat, Jun 27, 2009 at 11:48, Vladimir Prus<ghost at cs.msu.su> wrote:
>> A different thought: QtCreator has a "Discardable" flag plus a
>> "Discards" flag for every command.
>> A Step command can discard commands that reload the state that way.
>> Do you think it's worth the work?
>
> This might actually be reasonable. I am not sure how those flags work
> in QtCreators but it seems worthwhile to separate 'state updating'
> commands, and whenever commands line 'step' are emitted
>
> - Remove state updating commands from the queue
> - Ignore results of commands that are already send to GDB
>
> In fact, GDB now has *running notification, which is probably the most
> reliable indicator that we need to discard state updating commands -- because
> this notification is emitted by GDB core in all cases when target is run,
> including CLI commands and macros.
Sounds good.
> - Ignore results of commands that are already send to GDB
isn't this a problem with -var-update? (we might ignore changes)
Niko
More information about the KDevelop-devel
mailing list