Date: Fri, 14 Jan 2005 18:29:30 -0800 From: "Medi Montaseri" <mmontaseri@amcc.com> To: freebsd-amd64@freebsd.org Subject: amd64 and FreeBSD 5.2.1 Message-ID: <41E8800A.70005@amcc.com>
next in thread | raw e-mail | index | archive | help
Hi....I am having some problem porting my app to FreeBSD 5.2.1 on a amd64 and am wondering about the state of 5.2.1 before I dive into debugging.... FYI...my app works fine on 64 bit linux. My concerns are: 1- http://www.freebsd.org/releng/#schedule describes 5.2.1 as "FreeBSD 5.2 / 5.2.1 security fix branch (not officially supported)." What do you mean by "not supported"....should I use 5.3 2- I do'nt see gdb(1) on the 5.2.1 ISOs. Was this never ported ? I have found gdb-6 but that requires libm.so.3 which is not available on 5.2.1.... stopped there as I was getting into pre-req recursive rat hole... If gdb was not made available, should I interpret this as 5.2.1 is not a formal release? 3- I don't see any traces of 5.2.1 on FreeBSD mirror sites... as though it was there and now its not... This is worring me....was there something about 5.2.1 that has disappeared from the face of Internet. Or is it the FreeBSD.org practice of pulling down previous releases....maybe a minor issue...right now I'm over reading too much. 4- My motherboard is actually a dual CPU using Intel EM64T (Extended Memory) but uname -m shows amd64.....I hope this ok... 5- My app is failing consistingly as follows... (gdb) bt #0 0x00000002007014d8 in find_symdef () from /libexec/ld-elf.so.1 #1 0x0000000200700d1b in _rtld_bind () from /libexec/ld-elf.so.1 #2 0x0000000200700755 in _rtld_bind_start () from /libexec/ld-elf.so.1 #3 0x0000000000000247 in ?? () #4 0x0000000000000004 in ?? () #5 0x0000000000000002 in ?? () #6 0x0000000200b73960 in RC5_version () from /lib/libcrypto.so.3 #7 0x0000000000000002 in ?? () #8 0x0000000000000206 in ?? () #9 0x0000000200718600 in ?? () #10 0x00000000000001d3 in ?? () #11 0x0000000200b30453 in ERR_get_state () from /lib/libcrypto.so.3 #12 0x0000000200b2fbe1 in ERR_put_error () from /lib/libcrypto.so.3 #13 0x0000000200b40192 in BIO_new_file () from /lib/libcrypto.so.3 #14 0x0000000200ae3277 in X509_load_cert_crl_file () from /lib/libcrypto.so.3 #15 0x0000000200ae2e9d in X509_LOOKUP_file () from /lib/libcrypto.so.3 I've seen some conversations on ld-elf.so.1 available at http://lists.freebsd.org/pipermail/freebsd-current/2004-February/021414.html Where Kenneth Merry at FreeBSD org concludes... So, it looks like find_symdef() is returning a bogus value for def, and NULL for defobj, which causes a NULL pointer deference at line 197. Does this look familiar to anyone? Since I've got a core dump, I can look at more things if anyone has anything they'd like to see. Ken -- So...anyone knows anything about this ld-elf.so.1 problem.... Thank you
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41E8800A.70005>