Re: [GDB/MI] missing token in "stopped" output after -exec-run?

Joel Brobecker
2008-05-21T05:24:09Z

> Yes (and I've explicitly posted to the list about this change, quite
> some time before actually changing things). The situation is:

Oh sorry, I vaguely remember this discussion indeed.

> Does it cause any problems for you?

No problem whatsoever. I have a testcase in our testsuite that did check
for the token on the "*stopped" notification, but the intent was really
to check that a -var-update doesn't crash the debugger. So I relaxed
a little our test to accept the absence of token and that was it for me.

The purpose of my message was to inform you of the change, in case
it was not intended and somehow slipped through testing. Glad to be
wrong :).

--
Joel