Date: Wed, 17 Jan 2018 12:00:22 +1030 From: "O'Connor, Daniel" <darius@dons.net.au> To: Konstantin Belousov <kostikbel@gmail.com> Cc: Pedro Giffuni <pfg@FreeBSD.org>, FreeBSD Hackers <freebsd-hackers@freebsd.org> Subject: Re: examining Linux core file? Message-ID: <32C3FADA-073C-4942-B12F-AEB7F345766E@dons.net.au> In-Reply-To: <20180116095908.GQ1684@kib.kiev.ua> References: <bfe13557-55f1-a04a-1367-9cbb58075323@FreeBSD.org> <20180116095908.GQ1684@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 16 Jan 2018, at 20:29, Konstantin Belousov <kostikbel@gmail.com> = wrote: >>=20 >> My memory is sketchy but you may need to build a complete=20 >> cross-toolchain for that. Long-long ago we actually did that but the=20= >> resulting linux binaries were weird and needed branding always. >=20 > No cross-toolchain will help there. Problem is that the binary is = Linux, > while core is FreeBSD. There are enough details significant to the = debugger > that make such combination a new platform. Using ktrace / linux_kdump might help - or at least give some clues as = to where it's failing too. -- Daniel O'Connor "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?32C3FADA-073C-4942-B12F-AEB7F345766E>