From owner-freebsd-ports-bugs@FreeBSD.ORG Sat Nov 20 06:00:58 2004 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9371F16A4CE for ; Sat, 20 Nov 2004 06:00:58 +0000 (GMT) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 846E843D54 for ; Sat, 20 Nov 2004 06:00:58 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) iAK60wSD031052 for ; Sat, 20 Nov 2004 06:00:58 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.12.11/8.12.11/Submit) id iAK60w2S031051; Sat, 20 Nov 2004 06:00:58 GMT (envelope-from gnats) Date: Sat, 20 Nov 2004 06:00:58 GMT Message-Id: <200411200600.iAK60w2S031051@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Mark Linimon Subject: Re: ports/62377: strace hangs when running programs from command line X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Mark Linimon List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Nov 2004 06:00:58 -0000 The following reply was made to PR ports/62377; it has been noted by GNATS. From: Mark Linimon To: freebsd-gnats-submit@FreeBSD.org Cc: alex@semenyaka.ru, nge@cs.hmc.edu Subject: Re: ports/62377: strace hangs when running programs from command line Date: Fri, 19 Nov 2004 23:54:11 -0600 Adding to audit trail from email from maintainer: Subject: Re: FreeBSD ports Problem Reports for ports you maintain Date: Wednesday 20 October 2004 06:30 pm From: Alex Semenyaka I could not reproduce the problem described since May 2004. Strace is frequently used by me so I hope that the problem does not exist anymore and was inspired by the changes in the kernel code. SY, Alex ------------------------------------------------------- To submitter: does the problem still persist in 5.3R?