What does asynchronous stack unwinding mean?
Here is a part of the doc of sb-thread:terminate-thread:
The unwind caused by TERMINATE-THREAD is asynchronous, meaning that
eg. thread executing
(let (foo)
(unwind-protect
(progn
(setf foo (get-foo))
(work-on-foo foo))
(when foo
;; An interrupt occurring inside the cleanup clause
;; will cause cleanups from the current UNWIND-PROTECT
;; to be dropped.
(release-foo foo))))
might miss calling RELEASE-FOO despite GET-FOO having returned true if
the interrupt occurs inside the cleanup clause, eg. during execution
of RELEASE-FOO.
Documentation is written in a way that it seems that async stack unwinding means that thread termination can occur at the moment when the thread executes cleanup clause of unwind-protect, causing some parts of the cleanup clause to be not executed.
Is async stack unwinding exactly this thing or am I missing something? This definition doesn't really match my current background in asynchronous programming.
multithreading common-lisp sbcl
asked Nov 22 '18 at 9:08
OlegTheCatOlegTheCat
3,268917
add a comment |
Here is a part of the doc of sb-thread:terminate-thread:
The unwind caused by TERMINATE-THREAD is asynchronous, meaning that
eg. thread executing
(let (foo)
(unwind-protect
(progn
(setf foo (get-foo))
(work-on-foo foo))
(when foo
;; An interrupt occurring inside the cleanup clause
;; will cause cleanups from the current UNWIND-PROTECT
;; to be dropped.
(release-foo foo))))
might miss calling RELEASE-FOO despite GET-FOO having returned true if
the interrupt occurs inside the cleanup clause, eg. during execution
of RELEASE-FOO.
Documentation is written in a way that it seems that async stack unwinding means that thread termination can occur at the moment when the thread executes cleanup clause of unwind-protect, causing some parts of the cleanup clause to be not executed.
Is async stack unwinding exactly this thing or am I missing something? This definition doesn't really match my current background in asynchronous programming.
multithreading common-lisp sbcl
asked Nov 22 '18 at 9:08
OlegTheCatOlegTheCat
3,268917
1
Yes, asynchronous operations can happen at any unpredictable point in the normal execution of the program. Say you have threadsAandB. IfAcallsTERMINATE-THREADonB, whateverBhappens to be doing at the moment is interrupted with the instruction to terminate itself. You could useSB-SYS:WITHOUT-INTERRUPTSto prevent the interruption at certain parts of the program, but otherwise there is no way to predict when the order to terminate will arrive.
– jkiiski
Nov 23 '18 at 7:12
add a comment |
Here is a part of the doc of sb-thread:terminate-thread:
The unwind caused by TERMINATE-THREAD is asynchronous, meaning that
eg. thread executing
(let (foo)
(unwind-protect
(progn
(setf foo (get-foo))
(work-on-foo foo))
(when foo
;; An interrupt occurring inside the cleanup clause
;; will cause cleanups from the current UNWIND-PROTECT
;; to be dropped.
(release-foo foo))))
might miss calling RELEASE-FOO despite GET-FOO having returned true if
the interrupt occurs inside the cleanup clause, eg. during execution
of RELEASE-FOO.
Documentation is written in a way that it seems that async stack unwinding means that thread termination can occur at the moment when the thread executes cleanup clause of unwind-protect, causing some parts of the cleanup clause to be not executed.
Is async stack unwinding exactly this thing or am I missing something? This definition doesn't really match my current background in asynchronous programming.
multithreading common-lisp sbcl
asked Nov 22 '18 at 9:08
OlegTheCatOlegTheCat
3,268917
Here is a part of the doc of sb-thread:terminate-thread:
The unwind caused by TERMINATE-THREAD is asynchronous, meaning that
eg. thread executing
(let (foo)
(unwind-protect
(progn
(setf foo (get-foo))
(work-on-foo foo))
(when foo
;; An interrupt occurring inside the cleanup clause
;; will cause cleanups from the current UNWIND-PROTECT
;; to be dropped.
(release-foo foo))))
might miss calling RELEASE-FOO despite GET-FOO having returned true if
the interrupt occurs inside the cleanup clause, eg. during execution
of RELEASE-FOO.
Documentation is written in a way that it seems that async stack unwinding means that thread termination can occur at the moment when the thread executes cleanup clause of unwind-protect, causing some parts of the cleanup clause to be not executed.
Is async stack unwinding exactly this thing or am I missing something? This definition doesn't really match my current background in asynchronous programming.
multithreading common-lisp sbcl
multithreading common-lisp sbcl
asked Nov 22 '18 at 9:08
OlegTheCatOlegTheCat
3,268917
asked Nov 22 '18 at 9:08
OlegTheCatOlegTheCat
3,268917
asked Nov 22 '18 at 9:08
OlegTheCatOlegTheCat
3,268917
asked Nov 22 '18 at 9:08
OlegTheCatOlegTheCat
3,268917
asked Nov 22 '18 at 9:08
OlegTheCatOlegTheCat
3,268917
3,268917
1
Yes, asynchronous operations can happen at any unpredictable point in the normal execution of the program. Say you have threadsAandB. IfAcallsTERMINATE-THREADonB, whateverBhappens to be doing at the moment is interrupted with the instruction to terminate itself. You could useSB-SYS:WITHOUT-INTERRUPTSto prevent the interruption at certain parts of the program, but otherwise there is no way to predict when the order to terminate will arrive.
– jkiiski
Nov 23 '18 at 7:12
add a comment |
1
Yes, asynchronous operations can happen at any unpredictable point in the normal execution of the program. Say you have threadsAandB. IfAcallsTERMINATE-THREADonB, whateverBhappens to be doing at the moment is interrupted with the instruction to terminate itself. You could useSB-SYS:WITHOUT-INTERRUPTSto prevent the interruption at certain parts of the program, but otherwise there is no way to predict when the order to terminate will arrive.
– jkiiski
Nov 23 '18 at 7:12
1
1
Yes, asynchronous operations can happen at any unpredictable point in the normal execution of the program. Say you have threads
A and B. If A calls TERMINATE-THREAD on B, whatever B happens to be doing at the moment is interrupted with the instruction to terminate itself. You could use SB-SYS:WITHOUT-INTERRUPTS to prevent the interruption at certain parts of the program, but otherwise there is no way to predict when the order to terminate will arrive.– jkiiski
Nov 23 '18 at 7:12
Yes, asynchronous operations can happen at any unpredictable point in the normal execution of the program. Say you have threads
A and B. If A calls TERMINATE-THREAD on B, whatever B happens to be doing at the moment is interrupted with the instruction to terminate itself. You could use SB-SYS:WITHOUT-INTERRUPTS to prevent the interruption at certain parts of the program, but otherwise there is no way to predict when the order to terminate will arrive.– jkiiski
Nov 23 '18 at 7:12
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53427287%2fwhat-does-asynchronous-stack-unwinding-mean%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53427287%2fwhat-does-asynchronous-stack-unwinding-mean%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
1
Yes, asynchronous operations can happen at any unpredictable point in the normal execution of the program. Say you have threads
AandB. IfAcallsTERMINATE-THREADonB, whateverBhappens to be doing at the moment is interrupted with the instruction to terminate itself. You could useSB-SYS:WITHOUT-INTERRUPTSto prevent the interruption at certain parts of the program, but otherwise there is no way to predict when the order to terminate will arrive.– jkiiski
Nov 23 '18 at 7:12