This is the mail archive of the gdb-patches@sourceware.cygnus.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]

Re: [PATCH] GDB command-line switches and annotations docs


Eli Zaretskii writes:
 > 
 > Here are patches to gdb.texinfo and annotate.texi which add indexing
 > to command-line switches, document some switches that were not in the
 > manual, and make annotate.texi part of GDB manual.
 > 
 > (Are there plans to make gdbmi.texi be part of the manual as well?)
 > 

Eventually yes (Andrew?), right now it is not in prime time form yet. It is
still very rough work in progress.

 > +
 > +@item -async
 > +@cindex ---async
 > +Use the asynchronous event loop for the command-line interface.
 > +@value{GDBN} processes all events, such as user keyboard input, via a
 > +special event loop.  This allows @value{GDBN} to accept and process user
 > +commands in parallel with the debugged process being
 > +run@footnote{@value{GDBN} built with @sc{djgpp} tools for
 > +MS-DOS/MS-Windows supports this mode of operation, but the event loop is
 > +suspended when the debuggee runs.}, so you don't need to wait for
 > +control to return to @value{GDBN} before you type the next command.
 > +
 > +When the standard input is connected to a terminal device, @value{GDBN}
 > +uses the asynchronous event loop by default, unless disabled by the
 > +@samp{-noasync} option.
 > +
 > +@item -noasync
 > +@cindex ---noasync
 > +Disable the asynchronous event loop for the command-line interface.
 > +


I was planning on removing the -async option, it is now redundant.
Maybe I should just go ahead and do it now.
The --noasync stays there for the moment but my hope is that it will
eventually not be necessary anymore.  As far as the footnote goes,
that behavior is what you get in all the platforms and configurations
at the moment not just djgpp. The target side is not hooked up to the
event loop yet (except for a 'clone' of the remote target, called
'async'). So I would modify the above entry to specify that the event
loop right now involves only user events, not target ones. Eventually
it will deal with target side too, but each target needs to be
converted. The behavior you describe is the ultimate goal, we are only
about 50% there.

Elena

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