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


> Date: Thu, 13 Jun 2002 22:24:36 -0700 (PDT)
> From: Keith Seitz <keiths@redhat.com>
> 
> This is the promised gdbmi.texinfo proposal that I referred to in:
> 
> http://sources.redhat.com/ml/gdb/2002-06/msg00106.html
> 
> This patch formalizes events in MI. Specifically, I propose to whack
> notify-async-output from aync-record and add event-record to
> out-of-band-record.

Thanks.  This is approved, but please take care of teh following
small problems:

> ! in @value{GDBN}. Events can be generated by any command, whether that command

Please always leave two spaces after a period that ends a sentence.
This is important for the printed version to be typeset correctly by
TeX.

> ! @item breakpoint-create
> ! @item breakpoint-modify
> ! @item breakpoint-delete
> ! @item tracepoint-create
> ! @item tracepoint-modify
> ! @item tracepoint-delete
> ! A breakpoint or tracepoint was created, modified, or deleted. In all cases,

You cannot lump several @item's together, the result will look badly.
All the @item's but the first need to be an @itemx instead.

> ! @example
> ! =breakpoint-create,number="1"
> ! @end example

I believe the general policy in the GDB manual is to use @smallexample
throughout.


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