From owner-freebsd-emulation@FreeBSD.ORG Fri Jan 4 13:28:46 2013 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id F17353A0 for ; Fri, 4 Jan 2013 13:28:46 +0000 (UTC) (envelope-from mailinglists@martinlaabs.de) Received: from relay03.alfahosting-server.de (relay03.alfahosting-server.de [109.237.142.239]) by mx1.freebsd.org (Postfix) with ESMTP id B3CEB22E for ; Fri, 4 Jan 2013 13:28:46 +0000 (UTC) Received: by relay03.alfahosting-server.de (Postfix, from userid 1001) id 7797832C1D26; Fri, 4 Jan 2013 14:28:38 +0100 (CET) X-Spam-DCC: : X-Spam-Level: X-Spam-Status: No, score=0.0 required=7.0 tests=BAYES_50 autolearn=disabled version=3.2.5 Received: from alfa3018.alfahosting-server.de (alfa3018.alfahosting-server.de [109.237.140.30]) by relay03.alfahosting-server.de (Postfix) with ESMTP id 205E032C1D35 for ; Fri, 4 Jan 2013 14:28:37 +0100 (CET) Received: from pc.martinlaabs.de (p54B32E3A.dip.t-dialin.net [84.179.46.58]) by alfa3018.alfahosting-server.de (Postfix) with ESMTPSA id E5FF5515C343 for ; Fri, 4 Jan 2013 14:28:36 +0100 (CET) Message-ID: <50E6D903.7080306@martinlaabs.de> Date: Fri, 04 Jan 2013 14:28:35 +0100 From: Martin Laabs User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: freebsd-emulation@freebsd.org Subject: Debugging a linux application and library in freebsd Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Status: No X-Virus-Checker-Version: clamassassin 1.2.4 with ClamAV 0.97.3/16349/Fri Jan 4 12:57:07 2013 X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Jan 2013 13:28:47 -0000 Hi, I'm currently searching a bug in the linuxulator concerning a libc function. Therefore it would be very helpful using gdb to trace the program not only instruction for instruction but also with the source code and full symbols. Building the linux binary that reproduce the bug is done in a VM running an somewhat old debian. Building it with debugging symbols is also no problem. I could also imagine to build the libc with debugging symbols (if not available in some binary packages) Would you suggest to do this with a cross compiler under the linuxulator enviroment or in the debian VM? But anyway - the native gdb does not support linux binaries very well. So did anyone tried to run a linux gdb inside the linuxulator enviroment to trace the bug down into the library? Obviously the linux gdb does not know anything about the linux-call translation but this should be transparent to it. Thank you, Martin Laabs