From owner-freebsd-bugs@FreeBSD.ORG Wed Jan 9 00:30:01 2013 Return-Path: Delivered-To: freebsd-bugs@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3236A922 for ; Wed, 9 Jan 2013 00:30:01 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 247A07A6 for ; Wed, 9 Jan 2013 00:30:01 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r090U09W001510 for ; Wed, 9 Jan 2013 00:30:00 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r090U0im001507; Wed, 9 Jan 2013 00:30:00 GMT (envelope-from gnats) Date: Wed, 9 Jan 2013 00:30:00 GMT Message-Id: <201301090030.r090U0im001507@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Mark Johnston Subject: Re: bin/167103: dtrace(1) generates core dump trying to build perl with dtrace enabled X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: Mark Johnston List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jan 2013 00:30:01 -0000 The following reply was made to PR bin/167103; it has been noted by GNATS. From: Mark Johnston To: bug-followup@FreeBSD.org, swills@FreeBSD.org Cc: Subject: Re: bin/167103: dtrace(1) generates core dump trying to build perl with dtrace enabled Date: Tue, 8 Jan 2013 19:27:29 -0500 I've spent some more time digging into this and found a simple way to reproduce it. The problem only seems to occur when a probe is located in a static function. Some comments in dt_link.c indicate that there's some special handling that's needed in this case, but I still don't quite understand what's causing the problem. I've placed a simple provider definition and sample program that reproduce the issue here: http://people.freebsd.org/~markj/dtrace/bin167103/ When the repro program is built, dtrace(1) will segfault when processing the object file. When the patch attached to the PR is applied, dtrace will just exit with a generic error: dtrace -G -s provider.d repro.o provider: failed to link script provider: an error was encountered while processing repro.o *** [beforelinking] Error code 1 I'm still working on figuring this out. Thanks, -Mark