Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 13 Apr 2012 21:30:12 GMT
From:      Ryan Stone <rstone@FreeBSD.org>
To:        freebsd-gnats-submit@FreeBSD.org
Subject:   kern/166920: dtrace(1) kills itself with SIGUSR1
Message-ID:  <201204132130.q3DLUCvA060297@red.freebsd.org>
Resent-Message-ID: <201204132140.q3DLe5aN066315@freefall.freebsd.org>

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

>Number:         166920
>Category:       kern
>Synopsis:       dtrace(1) kills itself with SIGUSR1
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Apr 13 21:40:05 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator:     Ryan Stone
>Release:        8-STABLE
>Organization:
>Environment:
>Description:
(module-1:wheel)# dtrace -n 'database$pid:::' -c ./db
ld-elf.so.1: invalid probe specifier database$pid:::: failed to grab process 28055
User defined signal 1: 30

dtrace(1) sends itself SIGUSR1 (30) from one thread to another if it hits an error.  It would seem that in certain cases it sends that signal when there is no handler installed for it.
>How-To-Repeat:

>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:



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