nomagic

no, it is not magic !

User Tools

Site Tools


gdbs:notification_stop

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

gdbs:notification_stop [2025/06/02 16:42] – created larsgdbs:notification_stop [2025/06/02 16:45] (current) lars
Line 6: Line 6:
  
 Every notification’s data begins with a name, which contains no colon characters, followed by a colon character. 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.  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: The following notifications are defined:
 ^ Notification ^ Ack ^ Event ^ Description ^ ^ Notification ^ Ack ^ Event ^ Description ^
-| Stop | vStopped | reply: The reply has the form of a stop reply. |  Report an asynchronous stop event in non-stop mode. |+| 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> 
gdbs/notification_stop.txt · Last modified: by lars