Date: Mon, 13 Feb 2017 13:32:51 -0800 From: Conrad Meyer <cem@freebsd.org> To: Dimitry Andric <dim@freebsd.org> Cc: Eric McCorkle <eric@metricspace.net>, "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: GELI BIOS weirdness Message-ID: <CAG6CVpWiLm0%2BzP_LBFFn9izE7gdnh=icbqpKqjNS5v2_68TMrA@mail.gmail.com> In-Reply-To: <919F6E39-476C-44B5-93EA-447D855921DE@FreeBSD.org> References: <6874308d-8892-2f03-d125-418949fd472c@metricspace.net> <F1DCB7BA-0E21-44A6-B80A-0E0429B235FE@FreeBSD.org> <d4d9f6b2-4aaf-1c61-f7d5-f8be908bcc73@metricspace.net> <919F6E39-476C-44B5-93EA-447D855921DE@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
"objdump -D -b binary -Mx86-64 -mi386 foo.bin" should work fine (no symbols, though...). Best, Conrad On Mon, Feb 13, 2017 at 1:16 PM, Dimitry Andric <dim@freebsd.org> wrote: > On 13 Feb 2017, at 21:58, Eric McCorkle <eric@metricspace.net> wrote: >> >> On 02/13/2017 15:36, Dimitry Andric wrote: >> >>> This disassembles to: >>> >>> 0: 66 0f 38 f6 f0 adcx %eax,%esi >>> 5: 31 c6 xor %eax,%esi >>> 7: 8b 4d 14 mov 0x14(%ebp),%ecx >>> a: 89 cf mov %ecx,%edi >>> c: c1 ff 1f sar $0x1f,%edi >>> f: 8b .byte 0x8b >> >> Note that this was truncated, so the sar and .byte are probably a >> truncated instruction. >> >> Also, when I had printfs in place, I could see the call instructions. >> >>> My first guess would be that the code simply jumped into garbage. But >>> can you post the complete .o file somewhere for inspection? >> >> Attached. >> <gptboot> > > Can you please post the file before it's been stripped and objcopied > from ELF to binary format? That makes it a lot easier to disassemble > and analyze... :) > > -Dimitry >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAG6CVpWiLm0%2BzP_LBFFn9izE7gdnh=icbqpKqjNS5v2_68TMrA>