From owner-freebsd-hackers@FreeBSD.ORG Fri Jul 25 09:46:51 2003 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3359037B41E for ; Fri, 25 Jul 2003 09:46:51 -0700 (PDT) Received: from natto.numachi.com (natto.numachi.com [198.175.254.216]) by mx1.FreeBSD.org (Postfix) with SMTP id 1957E43F85 for ; Fri, 25 Jul 2003 09:46:50 -0700 (PDT) (envelope-from reichert@numachi.com) Received: (qmail 3436 invoked by uid 1001); 25 Jul 2003 16:46:49 -0000 Date: Fri, 25 Jul 2003 12:46:49 -0400 From: Brian Reichert To: hackers@freebsd.org Message-ID: <20030725164649.GF297@numachi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: recent mplayer port spinning? X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 Jul 2003 16:46:51 -0000 Dunno how much further I want to chase this, but I wanted to ask the world first: For FreeBSD 4.7-R, I just (as in two days ago) reinstalled all of my packages via ports (cvsupped nightly). Now, often, mplayer spins upon quitting. It does print "Exiting... (End of file)", then never actually quits, it spins, eating my CPU, and I jave to -KILL it. A ktrace shows me: 3230 mplayer RET write 1 3230 mplayer CALL write(0x1,0x84e4000,0x19) 3230 mplayer GIO fd 1 wrote 25 bytes "Exiting... (End of file) " 3230 mplayer RET write 25/0x19 3230 mplayer CALL getpid 3230 mplayer RET getpid 3230/0xc9e 3230 mplayer CALL getpid 3230 mplayer RET getpid 3230/0xc9e 3230 mplayer PSIG SIGSEGV caught handler=0x28a23568 mask=0x0 code=0x0 3230 mplayer CALL sigreturn(0x8440e7c) 3230 mplayer RET sigreturn JUSTRETURN 3230 mplayer PSIG SIGSEGV caught handler=0x28a23568 mask=0x0 code=0x0 3230 mplayer CALL sigreturn(0x8440e7c) 3230 mplayer RET sigreturn JUSTRETURN 3230 mplayer PSIG SIGSEGV caught handler=0x28a23568 mask=0x0 code=0x0 3230 mplayer CALL sigreturn(0x8440e7c) 3230 mplayer RET sigreturn JUSTRETURN ... I _do_ want to open a PR on this, but I'm uncertain if if I should just claim it's an mplayer issue, or should I do more research to track what the point of failure it 'really' is, or just open a PR describing my symptoms, as-is. Any advice? -- Brian 'you Bastard' Reichert 37 Crystal Ave. #303 Daytime number: (603) 434-6842 Derry NH 03038-1713 USA BSD admin/developer at large