* gdb.texinfo (GDB/MI Development and Front Ends):
Document *thread-created and *thread-exited.
This commit is contained in:
parent
063bfe2e12
commit
fa0f268daf
2 changed files with 6 additions and 5 deletions
|
@ -1,3 +1,8 @@
|
|||
2008-05-03 Vladimir Prus <vladimir@codesourcery.com>
|
||||
|
||||
* gdb.texinfo (GDB/MI Development and Front Ends):
|
||||
Document *thread-created and *thread-exited.
|
||||
|
||||
2008-05-03 Pedro Alves <pedro@codesourcery.com>
|
||||
|
||||
* observer.texi (thread_exit): New.
|
||||
|
|
|
@ -18062,11 +18062,7 @@ responsibility of the front end to work with the new one.
|
|||
The best way to avoid unexpected changes in MI that might break your front
|
||||
end is to make your project known to @value{GDBN} developers and
|
||||
follow development on @email{gdb@@sourceware.org} and
|
||||
@email{gdb-patches@@sourceware.org}. There is also the mailing list
|
||||
@email{dmi-discuss@@lists.freestandards.org}, hosted by the Free Standards
|
||||
Group, which has the aim of creating a more general MI protocol
|
||||
called Debugger Machine Interface (DMI) that will become a standard
|
||||
for all debuggers, not just @value{GDBN}.
|
||||
@email{gdb-patches@@sourceware.org}.
|
||||
@cindex mailing lists
|
||||
|
||||
@c %%%%%%%%%%%%%%%%%%%%%%%%%%%% SECTION %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
||||
|
|
Loading…
Reference in a new issue