StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POException thrown using boost thread library
primarykey
Id
18192923
data
AcceptedAnswerId
18193586
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-08-12T17:19:51.573
FavoriteCount
0
LastActivityDate
2013-08-13T12:42:28.120
LastEditDate
2013-08-13T12:38:45.883
LastEditorUserId
2532888
OwnerUserId
2532888
ParentId
0
PostTypeId
1
Score
0
ViewCount
493
LastEditorDisplayName
text
Body
I have the following code to run a timed thread: <pre><code>// Method to invoke a request with a timeout. bool devices::server::CDeviceServer::invokeWithTimeout(CDeviceClientRequest& request, CDeviceServerResponse& response) { // Retrieve the timeout from the device. int timeout = getTimeout(); timeout += 500; // Add 500ms to cover invocation time. // Invoke the request within a timed thread. boost::promise<void> boostPromise; boost::unique_future<void> boostFuture = boostPromise.get_future(); boost::thread boostThread([&]() { invoke(request, response); boostPromise.set_value(); }); // The thread has timed out, if the future is not ready. return (boostFuture.wait_for(boost::chrono::milliseconds(timeout)) == boost::future_status::ready); } </code></pre> This appears to work without a problem, the function returns false when it times out. However, then the code being invoked (by invoke(request, response);) throws an exception which kills the application. How do I successfully terminate the thread if it has not completed, and consume any exceptions. I have tried the following: <pre><code>// The thread has timed out, if the future is not ready. bool completed = (boostFuture.wait_for(boost::chrono::milliseconds(timeout)) == boost::future_status::ready); if (!completed) { boostThread.interrupt(); } return completed; </code></pre> But this also throws an exception and crashes the application. I need a completely safe mechanism where the timed thread can be safely killed off, if the timeout has been reached.
Tags
<c++><boost><boost-thread>
Title
Exception thrown using boost thread library
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USMarcus MacWilliam
UserOwnerUserId
1. USMarcus MacWilliam
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.