Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 20 Jan 2010 16:54:00 -0800 (PST)
From:      "Ronald F.Guilmette" <rfg@tristatelogic.com>
To:        FreeBSD-gnats-submit@FreeBSD.org
Subject:   ports/143043: xv-3.10a_{7,11} improperly ignores SIGTERM (ctrl-C)
Message-ID:  <20100121005400.DDF49BDC45@segfault.tristatelogic.com>
Resent-Message-ID: <201001210100.o0L10K3f031537@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help

>Number:         143043
>Category:       ports
>Synopsis:       xv-3.10a_{7,11} improperly ignores SIGTERM (ctrl-C)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Jan 21 01:00:19 UTC 2010
>Closed-Date:
>Last-Modified:
>Originator:     Ronald F. Guilmette
>Release:        FreeBSD 7.0-RELEASE i386
>Organization:
Infinite Monkeys & Co. LLC
>Environment:
System: FreeBSD segfault.tristatelogic.com 7.0-RELEASE FreeBSD 7.0-RELEASE #0: Tue Aug 5 02:38:40 PDT 2008 root@segfault.monkeys.com:/usr/src/sys/i386/compile/rfg20080805 i386

>Description:
	Since upgrading a number of my ports (including numerous libraries)
	in order to get other things to work, I noticed that xv-3.10a_7 was
	no longer responding at all to ctrl-C (SIGTERM).  So I did the obvious
	thing and did a portupgrade to the latest, xv-3.10a_11.  That has been
	installed, but the problem remains... xv-3.10a_11 is not responding to
	SIGTERM, e.g. while it is displaying a JPEG.

>How-To-Repeat:
	Step 1)
	  Run xv-3.10a_11 and give it a filename of a JPEG on the command line.
	Step 2)
	  Type a ctrl-C, or else go to another xterm window and run ps to find
	  the PID of the xv process and then do kill -15 <procno>
	
	Note that after Step 2, nothing happens.

	(Note that kill -9 still works however, but kill -15 should work also.
	It did so previously, and there's no reason it shouldn't work properly.)
>Fix:
	Beats me.  I guess that I could tear into the code to try to find out
	where it is _supposed_ to handle SIGTERM, but I'm sort of hoping that
	someone who is already familiar with this code will have a look see
	first.
>Release-Note:
>Audit-Trail:
>Unformatted:



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100121005400.DDF49BDC45>