[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] kernel: 4gb seg fixup messages...
On 14. Май 2009 10:38, Travis Bell wrote: > Hi Igor, > > [root@web1 ~]# ldconfig -p | grep libcrypt.so > libcrypt.so.1 (libc6, OS ABI: Linux 2.6.9) => /lib/libcrypt.so.1 > libcrypt.so (libc6, OS ABI: Linux 2.6.9) => /usr/lib/libcrypt.so > > AND > > [root@web1 ~]# ldconfig -p | grep libdl.so.2 > libdl.so.2 (libc6, OS ABI: Linux 2.6.9) => /lib/libdl.so.2 > > RE: RPM version of Ruby, not sure... never tried. You think that would > potentially help? Yes, it is very likely that it should help. Two libraries linked with your ruby process are not xenified (they use TLS). These are libcrypt.so and libdl.so. Also, in theory, your ruby process could use TLS itself. I've just started CentOS 5.2 installation on Amazon EC2 to check if ruby there uses the same libraries as yours do, and it uses! [root@ip-10-250-7-83:~] ldd `which ruby` linux-gate.so.1 => (0xb7faf000) libruby.so.1.8 => /usr/lib/libruby.so.1.8 (0xb7eb9000) libpthread.so.0 => /lib/i686/nosegneg/libpthread.so.0 (0xb7ea2000) libdl.so.2 => /lib/libdl.so.2 (0xb7e9e000) libcrypt.so.1 => /lib/libcrypt.so.1 (0xb7e6b000) libm.so.6 => /lib/i686/nosegneg/libm.so.6 (0xb7e44000) libc.so.6 => /lib/i686/nosegneg/libc.so.6 (0xb7cfe000) /lib/ld-linux.so.2 (0xb7fb0000) So it's very likely, that it is your ruby binary that uses TLS itself. Could you try ruby from RPM? -- Igor Chubin _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |