VDBDebuggerApplication.st
changeset 75 05177610d04d
parent 73 82e202dec6cb
child 83 101ff2210613
equal deleted inserted replaced
74:1a238ee98ed3 75:05177610d04d
   904     self updateButtonEnablements
   904     self updateButtonEnablements
   905 
   905 
   906     "Created: / 01-06-2017 / 23:43:00 / Jan Vrany <jan.vrany@fit.cvut.cz>"
   906     "Created: / 01-06-2017 / 23:43:00 / Jan Vrany <jan.vrany@fit.cvut.cz>"
   907 !
   907 !
   908 
   908 
   909 onExitEvent: aGDBStoppedEvent
   909 onExitEvent: aGDBExitEvent
       
   910     "/ Check if GDB terminateg gracefully, if not,
       
   911     "/ show warning and allow user to inspect the
       
   912     "/ record.
       
   913     "/ 
       
   914     "/ Yes, even GDB has bugs and crashes.
       
   915     aGDBExitEvent status status == #signal ifTrue:[ 
       
   916         (Dialog confirm: 
       
   917             (resources stringWithCRs: 'GDB terminated by signal %1 (%2)\Show MI trace?' 
       
   918                                 with: aGDBExitEvent status code 
       
   919                                 with:(OperatingSystem nameForSignal: aGDBExitEvent status code)))
       
   920             ifTrue:[  aGDBExitEvent trace inspect ]
       
   921     ].
   910     self closeDownViews
   922     self closeDownViews
   911 
   923 
   912     "Created: / 01-06-2017 / 13:42:25 / Jan Vrany <jan.vrany@fit.cvut.cz>"
   924     "Created: / 01-06-2017 / 13:42:25 / Jan Vrany <jan.vrany@fit.cvut.cz>"
       
   925     "Modified: / 28-05-2018 / 23:00:29 / Jan Vrany <jan.vrany@fit.cvut.cz>"
   913 !
   926 !
   914 
   927 
   915 onLogOutputEvent:aGDBLogOutputEvent 
   928 onLogOutputEvent:aGDBLogOutputEvent 
   916 
   929 
   917     Transcript nextPutAll: aGDBLogOutputEvent value.
   930     Transcript nextPutAll: aGDBLogOutputEvent value.