StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
1187905
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-07-27T12:27:33.660
FavoriteCount
0
LastActivityDate
2015-03-18T05:23:38.343
LastEditDate
2015-03-18T05:23:38.343
LastEditorUserId
2753241
OwnerUserId
143564
ParentId
1178902
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
Your application has to the opportunity to handle <kbd>Ctrl</kbd><kbd>C</kbd> and <kbd>Ctrl</kbd><kbd>Break</kbd>, as key strokes or signals (depends on config), meaning that the application has the opportunity to make a clean exit, these would be a much softer way to terminate a process, allowing it a little more execution time if nothing else. TerminateProcess is more of a kick in the teeth, the application cannot handle this, it comes from the kernel, and if the application could handle it, this would create all sorts of issues with 'un killable' processes hanging their TerminateProcess handler and refusing to exit. As I understand it as soon as TerminateProcess is called on the process, it can not execute anymore code thats it, no clean up, no shutdown, its just over, you cant handle it, it simply wouldn't make sense if you could, not from a security perspective. Excellent code project article here on handling windows console signals: <a href="http://www.codeproject.com/KB/winsdk/console_event_handling.aspx" rel="nofollow noreferrer">http://www.codeproject.com/KB/winsdk/console_event_handling.aspx</a> Implementing some of the above signal handling you could ensure that the database writes have a chance to complete before the program exits, rather than possibly leaving it to chance. You can block TerminateProcess, but its' not really 'polite' programming, it's more like root kit programming, I have seen a good article on this at rootkit.com so search there for 'Process Invincibility' once you have the invincible process, it could in its own time shut down after receiving such a 'request', and perform any clean up before hnad, but this most certainly a hack. It seems to me though that the <kbd>Ctrl</kbd><kbd>C</kbd> behaviour you are currently seeing is due it not immediately ending the running process.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POTerminateProcess vs Ctrl+C
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USudondan
UserOwnerUserId
1. USGavin
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. This table or related slice is empty.
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.