--- a/ProcessorScheduler.st	Thu Apr 19 10:48:30 2018 +0200
+++ b/ProcessorScheduler.st	Thu Apr 19 10:49:42 2018 +0200
@@ -883,11 +883,10 @@
         [:ex |
             (HaltInterrupt accepts:ex creator) ifTrue:[
                 "/ in a standalone application, we do not want those
-                (Smalltalk isStandAloneApp and:[Smalltalk isStandAloneDebug not]) ifTrue:[
+                (Smalltalk isDebuggableApp) ifTrue:[
                     ('Processor [info]: ignored (', ex creator printString, ')') infoPrintCR.
-                    ex proceed.
+                    "/ MiniDebugger enter. -- should this be done when some --debug/--verbose was given?
                 ].
-                "/ MiniDebugger enter. -- should this be done when some --debug/--verbose was given?
                 ex proceed.
             ].
 
@@ -917,8 +916,8 @@
 
     'Processor [info]: finish dispatch (no more processes)' infoPrintCR.
 
-    "Modified: / 23-09-1996 / 14:19:56 / stefan"
     "Modified: / 20-07-2012 / 18:34:48 / cg"
+    "Modified: / 19-04-2018 / 10:36:29 / stefan"
 ! !
 
 !ProcessorScheduler methodsFor:'initialization'!
@@ -1140,14 +1139,14 @@
         "/ ignore in standalone apps; enter a minidebugger if not.
         "/ it is (currently not clear, how this happens, but seems to be harmless)
         Logger warning:'Processor [warning]: bad vmSuspendInterrupt: process not on run list'.
-        "/ 'Processor [warning]: bad vmSuspendInterrupt: not on run list' errorPrintCR.
-        (Smalltalk isStandAloneApp and:[Smalltalk isStandAloneDebug not]) ifFalse:[
+        Smalltalk isDebuggableApp ifTrue:[
             MiniDebugger enterWithMessage:'bad vmSuspendInterrupt: not on run list' mayProceed:true.
         ].    
         ^ self
     ].
 
     "Modified: / 31-03-2017 / 13:12:49 / cg"
+    "Modified: / 19-04-2018 / 10:37:55 / stefan"
 ! !
 
 !ProcessorScheduler methodsFor:'os process handling'!