[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Kernel Issues (WAS Re: vim-enhanced oddness)



..thought I'd point out that reverting to kernel 2135 *eliminated* the problem I was seeing with vim-enhanced (writing to disk resulted in SIGILL's). I'll open a bugzilla ticket against 2163 on this issue I guess.

The only outstanding issue I've seen now is that if I set LD_ASSUME_KERNEL=2.2.5 I get the following odd errors (and this is with any binary, not just dmesg in the example below:

[ksnider dw1 dw ksnider]$ ldd `which uname`
libc.so.6 => /lib64/tls/libc.so.6 (0x0000003f53000000)
/lib64/ld-linux-x86-64.so.2 => /lib64/ld-linux-x86-64.so.2 (0x0000003f52e00000)
[ksnider dw1 dw ksnider]$ uname -a
Linux dw1.dw 2.4.22-1.2135.nptlsmp #1 SMP Mon Dec 15 15:45:38 EST 2003 x86_64 x86_64 x86_64 GNU/Linux
[ksnider dw1 dw ksnider]$ export LD_ASSUME_KERNEL=2.2.5
[ksnider dw1 dw ksnider]$ uname -a
uname: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
[ksnider dw1 dw ksnider]$ unset LD_ASSUME_KERNEL
[ksnider dw1 dw ksnider]$ uname -a
Linux dw1.dw 2.4.22-1.2135.nptlsmp #1 SMP Mon Dec 15 15:45:38 EST 2003 x86_64 x86_64 x86_64 GNU/Linux


Very odd, looks like something is munging the LD_LIBRARY_PATH perhaps with NPTL disabled?




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]