MBSP

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== notifications ======

These are packets that go from the gdb server to gdb.

A notification packet has the form ‘% data # checksum’, where data is the content of the notification, and checksum is a checksum of data, computed and formatted as for ordinary GDB packets. A notification’s data never contains ‘$’, ‘%’ or ‘#’ characters. Upon receiving a notification, the recipient sends no ‘+’ or ‘-’ to acknowledge the notification’s receipt or to report its corruption. 

Every notification’s data begins with a name, which contains no colon characters, followed by a colon character.

‘name:event’

Recipients should silently ignore corrupted notifications and notifications they do not understand. Recipients should restart timeout periods on receipt of a well-formed notification, whether or not they understand it. 



The following notifications are defined:
^ Notification ^ Ack ^ Event ^ Description ^
| Stop | vStopped | Target stopped executing. The reply has the form of a stop reply. |  Report an asynchronous stop event in non-stop mode. |

=== Example ===

notification : <code>%Stop:T0505:98e7ffbf;04:4ce6ffbf;08:b1b6e54c;thread:p7526.7526;core:0;</code>
ack from gdb to notification: <code>vStopped</code>