This is the mail archive of the gdb-patches@sources.redhat.com mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [RFC/MI] Event Records vs Commands


On Sat, 15 Jun 2002, Andrew Cagney wrote:


Try:

...want to document ``notify-async-output'' or (less likely?) replace it
with ``event-async-output''.

This is the approach I've taken with my next attempt (which also includes
the fixes recommended by Eli, following the convention with two spaces
after @value{GDBN} -- if people want me to switch them all to use @., I
can submit separate patch for that).


Async output is anything that isn't bound to ``^done'' et.al. >

But it seems to be bound to the prompt. Apple has changed their version so
that it is NOT bound to the prompt. We'll need to discuss this sometime
later.
Ah, dig dig.

The idea was that ``\n(gdb)'' would act as a terminal signal for asynchronous events.

That way you would see:

event message
event message
(gdb)

<time passes>

event emssage
(gdb)

<time passes>

and not:

event message
event message

<time passes>

event message
.
.

however, yes, open to negotiation.

Andrew




Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]