glibc - Why would the same binary want linux-vdso.so.1 on one 64-bit RHEL 5.4 server and not another? -
I have a client running a file parsing program called cleanfileg, and as the last update, it receives the date format error Is parsing a file It is weird that both of us are running the same program, on the same file, with the creation of GCC, Pathrid, Library etc. Similar release of RHEL64 (5.4) and I can not repeat my problem, it can roll back the previous month version of cleanfile and everything works fine, so I'm pretty sure that the line-to-line The possibility of me will get an answer, but the deceptive thing to me is that on one wave it was asked to run an LDD on its executable, whether it was pulling in some different verions of the shared objects. Defense was. -min What is something like Linux-vdso.so.1 Needed (or not) required by configuring in some way? Any next step can anyone suggest for debugging? What Linux-vdso.a. 1 Is there anything that is needed (or not) according to any kind of need through configuration?
# ldd cleanfileg linux-vdso.so .1 = & gt; (0x00002ad4c98d1000) libmdGeo.so = & gt; /tools/clean_address/bin/libmdGeo.so (0x00002ad4c98d6000) libmdName.so = & gt; /tools/clean_address/bin/libmdName.so (0x00002ad4c9a70000) libmdPhone.so = & gt; /tools/clean_address/bin/libmdPhone.so (0x00002ad4c9df1000) libmdAddr.so = & gt; /tools/clean_address/bin/libmdAddr.so (0x00002ad4ca28c000) libresolv.so.2 = & gt; /lib64/libresolv.so.2 (0x0000003833600000) libAddressDoctor5.so = & gt; /tools/clean_address/bin/libAddressDoctor5.so (0x00002ad4ca96d000) libstdc ++ So.6 = & gt; /usr/lib64/libstdc++.so.6 (0x0000003831600000) libm.so.6 = & gt; /lib64/libm.so.6 (0x000000382b200000) libgcc_s.so.1 = & gt; /lib64/libgcc_s.so.1 (0x0000003830a00000) libpthread.so.0 = & gt; /lib64/libpthread.so.0 (0x000000382ba00000) libc.so.6 = & gt; / Lib64 / libc.so.6 (0x000000382ae00000) librt.so.1 = & gt; /lib64/librt.so.1 (0x000000382d200000) /lib64/ld-linux-x86-64.so.2 (0x000000382aa00000)
#ldd cleanfileg libmdGeo.so (0x00002ab5d3342000) libmdName.so (0x00002ab5d34cf000) libmdPhone.so (0x00002ab5d3850000) libmdAddr.so (0x00002ab5d3ceb000) libresolv.so.2 = & gt; /lib64/libresolv.so.2 (0x00000034bde00000) libAddressDoctor5.so (0x00002ab5d43bf000) libstdc ++ So.6 = & gt; /usr/lib64/libstdc++.so.6 (0x00000034c9000000) libm.so.6 = & gt; /lib64/libm.so.6 (0x00000034b6200000) libgcc_s.so.1 = & gt; /lib64/libgcc_s.so.1 (0x00000034c7c00000) libpthread.so.0 = & gt; /lib64/libpthread.so.0 (0x00000034b6a00000) libc.so.6 = & gt; / Lib64 / libc.so.6 (0x00000034b5e00000) librt.so.1 = & gt; /lib64/librt.so.1 (0x00000034b6e00000) /lib64/ld-linux-x86-64.so.2 (0x00000034b5a00000)
linux-vdso.so.1 is a "library" that is injected into every process by the kernel.
Comments
Post a Comment