From owner-freebsd-hackers@freebsd.org Tue Dec 22 22:58:42 2015 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 705BAA50F97 for ; Tue, 22 Dec 2015 22:58:42 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from bigwig.baldwin.cx (bigwig.baldwin.cx [IPv6:2001:470:1f11:75::1]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 523691171; Tue, 22 Dec 2015 22:58:42 +0000 (UTC) (envelope-from jhb@freebsd.org) Received: from ralph.baldwin.cx (c-73-231-226-104.hsd1.ca.comcast.net [73.231.226.104]) by bigwig.baldwin.cx (Postfix) with ESMTPSA id A44D3B94C; Tue, 22 Dec 2015 17:58:40 -0500 (EST) From: John Baldwin To: Ed Maste Cc: "freebsd-hackers@freebsd.org" Subject: Re: lldb crashes hello.c Date: Tue, 22 Dec 2015 14:58:37 -0800 Message-ID: <6983779.y0Y8FR9jyN@ralph.baldwin.cx> User-Agent: KMail/4.14.3 (FreeBSD/10.2-STABLE; KDE/4.14.3; amd64; ; ) In-Reply-To: References: <20151218190616.GA2284@becker.bs.l> <10631378.9HXCB454Uo@ralph.baldwin.cx> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.2.7 (bigwig.baldwin.cx); Tue, 22 Dec 2015 17:58:40 -0500 (EST) X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Dec 2015 22:58:42 -0000 On Tuesday, December 22, 2015 05:36:17 PM Ed Maste wrote: > On 21 December 2015 at 18:24, John Baldwin wrote: > > > > What about a FreeBSD/i386 binary on an amd64 host? > > Right now, no: > (lldb) run > Process 96045 launching > failed to fetch ps_strings: Bad address gdb7 can't run an i386 on amd64 either. It can attach to a running binary ok, but it gets confused because the embedded RTLD interpreter points to the amd64 RTLD. -- John Baldwin