From owner-freebsd-bugs@FreeBSD.ORG Fri Apr 13 21:30:12 2012 Return-Path: Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 18BB51065676 for ; Fri, 13 Apr 2012 21:30:12 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id E6A5B8FC14 for ; Fri, 13 Apr 2012 21:30:11 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q3DLUBTG055609 for ; Fri, 13 Apr 2012 21:30:11 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q3DLUBi5055608; Fri, 13 Apr 2012 21:30:11 GMT (envelope-from gnats) Resent-Date: Fri, 13 Apr 2012 21:30:11 GMT Resent-Message-Id: <201204132130.q3DLUBi5055608@freefall.freebsd.org> Resent-From: FreeBSD-gnats-submit@FreeBSD.org (GNATS Filer) Resent-To: freebsd-bugs@FreeBSD.org Resent-Reply-To: FreeBSD-gnats-submit@FreeBSD.org, Ryan Stone Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id A8F31106566B for ; Fri, 13 Apr 2012 21:28:25 +0000 (UTC) (envelope-from nobody@FreeBSD.org) Received: from red.freebsd.org (red.freebsd.org [IPv6:2001:4f8:fff6::22]) by mx1.freebsd.org (Postfix) with ESMTP id 7AF818FC14 for ; Fri, 13 Apr 2012 21:28:25 +0000 (UTC) Received: from red.freebsd.org (localhost [127.0.0.1]) by red.freebsd.org (8.14.4/8.14.4) with ESMTP id q3DLSPbs060225 for ; Fri, 13 Apr 2012 21:28:25 GMT (envelope-from nobody@red.freebsd.org) Received: (from nobody@localhost) by red.freebsd.org (8.14.4/8.14.4/Submit) id q3DLSPWS060224; Fri, 13 Apr 2012 21:28:25 GMT (envelope-from nobody) Message-Id: <201204132128.q3DLSPWS060224@red.freebsd.org> Date: Fri, 13 Apr 2012 21:28:25 GMT From: Ryan Stone To: freebsd-gnats-submit@FreeBSD.org X-Send-Pr-Version: www-3.1 Cc: Subject: kern/166919: If dtrace(1) crashes while attached to a process, the process is left in a weird state X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Apr 2012 21:30:12 -0000 >Number: 166919 >Category: kern >Synopsis: If dtrace(1) crashes while attached to a process, the process is left in a weird state >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Fri Apr 13 21:30:11 UTC 2012 >Closed-Date: >Last-Modified: >Originator: Ryan Stone >Release: 8-STABLE >Organization: >Environment: >Description: If I use dtrace -p to attach to a process and dtrace exits abnormally, the target process is left in a weird state and the only way to recover is to restart the process. >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted: