From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 17909 invoked by alias); 28 Mar 2013 16:45:23 -0000 Mailing-List: contact systemtap-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Post: List-Help: , Sender: systemtap-owner@sourceware.org Received: (qmail 17889 invoked by uid 89); 28 Mar 2013 16:45:14 -0000 X-Spam-SWARE-Status: No, score=-7.7 required=5.0 tests=AWL,BAYES_00,KHOP_RCVD_UNTRUST,KHOP_THREADED,RCVD_IN_DNSWL_HI,RCVD_IN_HOSTKARMA_W,RP_MATCHES_RCVD,SPF_HELO_PASS autolearn=ham version=3.3.1 Received: from mx1.redhat.com (HELO mx1.redhat.com) (209.132.183.28) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Thu, 28 Mar 2013 16:45:11 +0000 Received: from int-mx09.intmail.prod.int.phx2.redhat.com (int-mx09.intmail.prod.int.phx2.redhat.com [10.5.11.22]) by mx1.redhat.com (8.14.4/8.14.4) with ESMTP id r2SGjA56027466 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Thu, 28 Mar 2013 12:45:10 -0400 Received: from [10.3.113.92] (ovpn-113-92.phx2.redhat.com [10.3.113.92]) by int-mx09.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id r2SGjAaf016562 for ; Thu, 28 Mar 2013 12:45:10 -0400 Message-ID: <51547396.4070206@redhat.com> Date: Thu, 28 Mar 2013 16:45:00 -0000 From: Josh Stone User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4 MIME-Version: 1.0 To: systemtap@sourceware.org Subject: Re: user-space tracing on Debian... or..? References: <1363106084419-225167.post@n7.nabble.com> <84obeo8jbs.fsf@sauna.l.org> <1363160027043-225252.post@n7.nabble.com> <20130313142814.GA2263@redhat.com> <1363355658749-225525.post@n7.nabble.com> <1364466368978-226775.post@n7.nabble.com> <51546EFE.9040506@redhat.com> In-Reply-To: <51546EFE.9040506@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-SW-Source: 2013-q1/txt/msg00274.txt.bz2 On 03/28/2013 09:25 AM, Josh Stone wrote: > Is your libdwarf static? There is a thread discussing issues with this > on the dyninst-api list: > https://lists.cs.wisc.edu/archive/dyninst-api/2013/msg00026.shtml Now I feel I should suggest some actual solution too. :) We could probably add a link test during configure, trying a small test first with just -ldyninstAPI, and if that fails we can try again with the whole-archive -ldwarf options added.