[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Help-smalltalk] [PATCH 2/2] visualgst: Avoid live-lock on single-step d

From: Holger Hans Peter Freyther
Subject: [Help-smalltalk] [PATCH 2/2] visualgst: Avoid live-lock on single-step debugging
Date: Mon, 5 May 2014 13:48:37 +0200

Debugging "3 negated" and pressing "F7" could result in a
live-lock. While the dispatch routine of the mainloop was
ran the call-in process could wait on the "finalSemaphore"
and the "idle" process would be selected to execute as the
only process that remained runnable. This live-lock would
never be exited.

The underlying issue is that VisualGST is running in the
same image and can be impacted by the execution of the
debugged process. The only thing we can do right now is
to skip dangerous routines.

Currently the dangerous routines are related to the handling
of finalizers as the Glib/Gtk+ bindings create a lot of to
be finalized objects.

2014-05-05  Holger Hans Peter Freyther  <address@hidden>

        * Debugger/ Introduce >>#finishDangerousContexts
        and call it from >>#debugWith:.
 packages/visualgst/ChangeLog               |  5 +++++
 packages/visualgst/Debugger/ | 18 ++++++++++++++++++
 2 files changed, 23 insertions(+)

diff --git a/packages/visualgst/ChangeLog b/packages/visualgst/ChangeLog
index 330b439..4451f6e 100644
--- a/packages/visualgst/ChangeLog
+++ b/packages/visualgst/ChangeLog
@@ -1,3 +1,8 @@
+2014-05-05  Holger Hans Peter Freyther  <address@hidden>
+       * Debugger/ Introduce >>#finishDangerousContexts
+       and call it from >>#debugWith:.
 2014-02-10  Gwenael Casaccio  <address@hidden>
        * Source/ Display instance side and class side 
diff --git a/packages/visualgst/Debugger/ 
index 7c6983d..cea52c5 100644
--- a/packages/visualgst/Debugger/
+++ b/packages/visualgst/Debugger/
@@ -303,12 +303,30 @@ GtkBrowsingTool subclass: GtkDebugger [
         self debugWith: [ debugger finish ]
+    finishDangerousContexts [
+        | methods |
+        "VisualGST is running in the same image as the to be de-bugged
+        processed. If the process is suspended in a critical section
+        VisualGST might end up in a live-lock. As long as VisualGST is
+        running in the same image there is no way we can avoid this."
+        "Nothing is suspended."
+        debugger suspendedContext ifNil: [^self].
+        "Methods we need to finish or bad things will happen."
+        methods := {Object>>#removeToBeFinalized. Object>>#addToBeFinalized}.
+        (methods includes: debugger suspendedContext method)
+            ifTrue: [debugger finish].
+    ]
     debugWith: aBlock [
         <category: 'execute events'>
         TaskQueue uniqueInstance add: [
             self isLastContextSelected ifFalse: [ self stepToSelectedContext ].
             aBlock value.
+            self finishDangerousContexts.
             self updateContextWidget ]

reply via email to

[Prev in Thread] Current Thread [Next in Thread]