Date: Fri, 22 Feb 2013 20:35:46 +0400 From: Lev Serebryakov <lev@FreeBSD.org> To: Dimitry Andric <dimitry@andric.com> Cc: freebsd-current <freebsd-current@freebsd.org> Subject: Re: r245741 (clang as cc) can not build binaries for GEODE processor Message-ID: <562473731.20130222203546@serebryakov.spb.ru> In-Reply-To: <5127997A.2000901@andric.com> References: <108875110.20130222104603@serebryakov.spb.ru> <51277EFE.4000703@andric.com> <15917508.20130222194954@serebryakov.spb.ru> <5127997A.2000901@andric.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, Dimitry. You wrote 22 =D1=84=D0=B5=D0=B2=D1=80=D0=B0=D0=BB=D1=8F 2013 =D0=B3., 20:14= :50: DA> Maybe samba, or any of its dependencies, attempts to be "smart", and DA> enables some custom CPU optimizations? Maybe. I'll investigate this one too. >> DA> In any case, can you attempt to figure out which exact instructions = it >> DA> dies on? If gdb does not work, like you said above, maybe you can u= se >> DA> objdump to disassemble the executable in question, and find the addr= ess >> DA> of the failing instruction. >> I'm trying to do this with very last sources both as build system >> and target sources. DA> As Joerg Sonnenberger mentioned to me, the address 0x10351d6 you show in DA> the gdb session seems to be quite high, possibly pointing to some shared DA> library. Maybe you can try to figure out which library it is? I don't like "bt" result with only two lines in high addresses. I'm rebuilding NanoBSD image with enabled gdb now to run "testconf" under gdb itself. --=20 // Black Lion AKA Lev Serebryakov <lev@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?562473731.20130222203546>