[Bug 71132] New: Stop build should send SIGINT instead of SIGTERM

[0mecir at pauli.fmph.uniba.sk]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
     
http://bugs.kde.org/show_bug.cgi?id=71132     
           Summary: Stop build should send SIGINT instead of SIGTERM
           Product: kdevelop
           Version: unspecified
          Platform: Mandrake RPMs
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-devel at kdevelop.org
        ReportedBy: 0mecir at pauli.fmph.uniba.sk


Version:           3.0beta1 (using KDE KDE 3.1.2)
Installed from:    Mandrake RPMs
OS:          Linux

Stop Build sends the SIGTERM signal in order to stop the build. Problem is, that make doesn't remove unfinished output files when it receives this signal, so, if you then build again without any change to sources that would cause the interrupted file to compile again, make gets confused by (zero-size) .o file and doesn't build the .cpp file again. I found out that make removes unfinished object file when it receives SIGINT (ctrl+c) and that SIGTERM is not really required - SIGINT terminates make correctly.

Therefore, I suggest that SIGINT is sent to make instead of SIGTERM.