This is the mail archive of the gdb-prs@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]

gdb/603: MI: output -> (out-of-band-record)* [result-record] (out-of-band-record)* "(gdb)" nl


>Number:         603
>Category:       gdb
>Synopsis:       MI: output -> (out-of-band-record)* [result-record] (out-of-band-record)* "(gdb)" nl
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jul 10 14:58:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     ac131313@redhat.com
>Release:        2002-07-10
>Organization:
>Environment:

>Description:
GregW writes:

3. The gdb/mi output syntax in the manual does not quite reflect reality. In particular the 'console-stream-output', 'target-stream-output' and 'log-stream-output' rules should be suffixed with 'nl'.  Also, I've observed an 'out-of-band-record' appearing after a 'result-record' but the syntax doesn't allow this. I guess it should be something like:

output -> (out-of-band-record)* [result-record] (out-of-band-record)* "(gdb)" nl

--

I suspect the place to put the NL is in <out-of-band-record> removing the NL from <async-class>.
>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


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