Home Page
RABiD BUNNY FEVER
K.T.K

  • April 12, 2021, 08:22:47 PM *
  • Welcome, Guest
Please login or register.

Login with username, password and session length
Advanced search  

News:

Official site launch very soon, hurrah!


Author Topic: Cygwin SIGINT fix for golang  (Read 4203 times)

Dakusan

  • Programmer Person
  • Administrator
  • Hero Member
  • *****
  • Posts: 527
    • View Profile
    • Dakusan's Domain
Cygwin SIGINT fix for golang
« on: July 29, 2013, 09:52:49 AM »

Original post for Cygwin SIGINT fix for golang can be found at https://www.castledragmire.com/Posts/Cygwin_SIGINT_fix_for_golang.
Originally posted on: 07/29/13

Cygwin has had a long time problem that, depending on your configuration, may cause you to be unable to send a SIGINT (interrupt signal via Ctrl+C) to a native Windows command line executables. As a matter of fact, trying to do so may completely freeze up the console, requiring a process kill of the actual console, bash, and the executable you ran. This problem can crop up for many reasons including the version of Cygwin you are running and your terminal emulator. I specifically installed mintty as my default Cygwin console to get rid of this problem a long time ago (among many other features it had), and now it even has this problem.

While my normal solution is to try and steer clear of native Windows command line executables in Cygwin, this is not always an option. Golang was also causing me this problem every time I ran a network server, which was especially problematic as I would have to ALSO manually kill the server process or it would continue to hold the network port so another test of the code could not use it. An example piece of code is as follows:


package main
import ( "net/http"; "fmt" )
func main() {
   var HR HandleRequest
   if err := http.ListenAndServe("127.0.0.1:81", HR); err!=nil {
      fmt.Println("Error starting server") }
}

//Handle a server request
type HandleRequest struct{}
func (HR HandleRequest) ServeHTTP(w http.ResponseWriter, req *http.Request) {
   fmt.Printf("Received connection from: %s\n", req.RemoteAddr)
}
---

go run example.go

The first solution I found to this problem, which is by far the best solution, was to build the executable and then run it, instead of just running it straight from go.

go build example.go && example.exe
However, as of this post, it seems to no longer work! The last time I tested it and confirmed it was working was about 3 months ago, so who knows what has changed since then.

The second solution is to just build in some method of killing the process that uses “os.Exit”. For example, the following will exit if the user types “exit”

func ListenForExitCommand() {
   for s:=""; s!="exit"; { //Listen for the user to type exit
      if _, err:=fmt.Scanln(&s); err!=nil {
         if err.Error()!="unexpected newline" {
            fmt.Println(err) }
      } else if s=="flush" || s=="exit" {
         //Clean up everything here
      }
   }
   fmt.Println("Exit received, closing process")
   os.Exit(1)
}
and then add the following at the top of the main function:

go ListenForExitCommand() //Listen for "exit" command
Logged