From: Vladimir Prus Date: Sat, 3 May 2008 15:36:24 +0000 (+0000) Subject: * gdb.texinfo (GDB/MI Development and Front Ends): X-Git-Url: https://git.libre-soc.org/?a=commitdiff_plain;h=fa0f268daf0bea16c9e8f5cc17c3a076b0863aa2;p=binutils-gdb.git * gdb.texinfo (GDB/MI Development and Front Ends): Document *thread-created and *thread-exited. --- diff --git a/gdb/doc/ChangeLog b/gdb/doc/ChangeLog index afcdb9b4282..00e4de2d1bb 100644 --- a/gdb/doc/ChangeLog +++ b/gdb/doc/ChangeLog @@ -1,3 +1,8 @@ +2008-05-03 Vladimir Prus + + * gdb.texinfo (GDB/MI Development and Front Ends): + Document *thread-created and *thread-exited. + 2008-05-03 Pedro Alves * observer.texi (thread_exit): New. diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo index 7abac3c4b88..91c9dee7587 100644 --- a/gdb/doc/gdb.texinfo +++ b/gdb/doc/gdb.texinfo @@ -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 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%