From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 15 18:00:08 2008 Return-Path: Delivered-To: freebsd-amd64@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5889D1065673 for ; Mon, 15 Sep 2008 18:00:08 +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 3E3AB8FC17 for ; Mon, 15 Sep 2008 18:00:08 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.14.2/8.14.2) with ESMTP id m8FI08bi034679 for ; Mon, 15 Sep 2008 18:00:08 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.2/8.14.1/Submit) id m8FI08uS034678; Mon, 15 Sep 2008 18:00:08 GMT (envelope-from gnats) Date: Mon, 15 Sep 2008 18:00:08 GMT Message-Id: <200809151800.m8FI08uS034678@freefall.freebsd.org> To: freebsd-amd64@FreeBSD.org From: Dominic Fandrey X-Mailman-Approved-At: Mon, 15 Sep 2008 18:03:55 +0000 Cc: Subject: Re: amd64/127275: ldd(1) produces uncatchable output X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Dominic Fandrey List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2008 18:00:08 -0000 The following reply was made to PR amd64/127275; it has been noted by GNATS. From: Dominic Fandrey To: bug-followup@FreeBSD.org, kamikaze@bsdforen.de Cc: Subject: Re: amd64/127275: ldd(1) produces uncatchable output Date: Mon, 15 Sep 2008 19:51:14 +0200 This can be closed, because what I thought were two distinct problems has turned out to have the same cause. So this can be considered a duplicate of amd64/127276. Ldd invokes the binary and in case of a nonsensical elf-brand the kernel (at least that is my suspect) posts a message on the terminal. The workaround is to only run ldd on FreeBSD binaries. The safe solution, would in my opinion, be a check weather the binary uses the FreeBSD linker, but this discussion can remain in amd64/127276.