windows - TerminateProcess vs Ctrl+C -

-

I have a console-mode program that uses SQLite3 to maintain the database file. It takes some time to execute, but it should be secured at any time to cancel it, assuming that the database writes. (This is all under Windows)

To kill Ctrl c in the console compared to any of the consoles, Is anyone safe from the point but another program calls terminetproves?

I have seen that if TerminateProcess is called then I can get database corruption - I think it is because the program does not get the chance to write. My guess is that Ctrl C is better, because the program indicates and kills the OS rather than terminating it.

Note that the program does not actually handle the signal (unless it does not compute); I'm talking about the underlying default mechanism of Win32 executable to handle the Ctrl C signal.

To make the question clear / simple that this writing is currently executed: 

  stills (buff, 1024 * 1024, 1, stream); Class = "post-text" itemprop = "text"> 
 These are all binding arguments, but the only way to know this is to try it, Wrote a simple program that allocates a 1GB buffer, some data specifies it, and then writes it using a file (fwrite). I tried several ways to write "corrupt" data (especially I was hoping for a small file): 
 
     
  •  Calling TerminusPrice (Pearl's kill function and Win32: : 
    •  
  •  Using Task Manager's "End Process" 
    •  
  •  Using Process Explorer, "   Kill the process "
    •  
 
 In every case writing will not stop, the file was the correct size and the correct data was. And although "kill" will happen instantly, the process would have been until the writing was completed. 
 
 It seems that there is no difference between Terminate Process and  Ctrl   C  to see from the I / O point - once the start of writing It is guaranteed to be completed (excluding electricity outage).

Comments

Post a Comment

Popular posts from this blog

c# - ListView onScroll event -

-
I am programming a simple C # application, and I need a Scallow event on the list view. So I inherited the original ListView class created in ListviewEx witch. I found out how to locate the scroll message from WinAPI and I modified the WndProc method. Now I have this WndProc: protected override zero WndProc (Ref message message) {base.WndProc (Ref I); If (m.msg == WM_VSCROLL) {onScroll (This, New EventArgs ()); }} But the problem is, I do not know how to know about scrolling information. This data should be in wParam, but there is a LOWORD macro ++ like in C in C # and I switch to find the criteria like SB_ below, SB_ENDSCROLL, SB_PAGEUP etc. there any way Need to change the LOWORD macro from C #? Or any other way to find the necessary parameters about scrolling? You can define the WParam constants as the following: Private const int WM_HSCROLL = 0x114; Private Constant WM_VSCROLL = 0x115; Private contact int SBHOZZ = 0; Private Consultant SB_VERT = 1; Private Con...
Read more

PHP - get image from byte array -

-
I am trying to create a back-end for my mobile application. I am sending the content of an image in the body of the HTTP request (output stream) as a byte array, I want to read this stream of bytes in PHP scripts and take back an image. Can anyone tell me how can I do this? Thank you. You can obtain the request body $ body = Reading from file_get_contents ('php: // input'); What you do with that data Depending on you, you can write the data in a file as you mentioned that this is image data, you can drop the data into the object can do. Another option is to use and load the image.
Read more

Linux Terminal Problem with Non-Canonical Terminal I/O app -

-
I have a small app written in C to run on Linux. Part of the app accepts user-input from keyboard , And it uses non-canonical terminal mode so that it can respond to each keystroke. The section of the code that accepts input is a simple task that is called repeatedly in the loop: char get_input () {char C = 0; Int res = reading (input_tamille, & amp; c, 1); If (RSS == 0) 0 returns; If (res == -1) {/ * snip error handling * /} return c; } It reads a letter from the terminal if there is no input within a given time limit, (c_cc [VTIME] value in the vocabulary structure), read () 0 And get_input () is called again It all works very well, I have recently discovered that if you run this app in a terminal window, and then the app Close the terminal window without ending, the app will not exit Received, but CPU intensive launches into an infinite loop, where the read () returns 0 without waiting continued. So how can I get out of the apple if it runs from the terminal win...
Read more