thr3ads.net - Xen users - [Xen-users] segmentation fault in xen nslookup [Jul 2005]

If this information is useful, please help other people find it:
Share via:

Shahzad Chohan

2005-Jul-29 09:37 UTC

[Xen-users] segmentation fault in xen nslookup

Hi Guys,

I just managed to get rhel-3-ws working as a domU. The problem is that
when I run the following nslookup command I get a segmentaion fault.
Can anyone please shed a light on this. I''ve attached an strace, if it
helps.

nslookup 10.222.4.233
Segmentation fault
[root@rhel-3-ws root]# strace nslookup 10.222.4.233
execve("/usr/bin/nslookup", ["nslookup",
"10.222.4.233"], [/* 24 vars */]) = 0
uname({sys="Linux", node="rhel-3-ws", ...}) = 0
brk(0)                                  = 0x80566e8
open("/etc/ld.so.preload", O_RDONLY)    = -1 ENOENT (No such file or
directory)
open("/etc/ld.so.cache", O_RDONLY)      = 3
fstat64(3, {st_mode=S_IFREG|0644, st_size=75053, ...}) = 0
old_mmap(NULL, 75053, PROT_READ, MAP_PRIVATE, 3, 0) = 0x40016000
close(3)                                = 0
open("/usr/lib/libdns.so.8", O_RDONLY)  = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\300\35"...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1021048, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0x40029000
old_mmap(NULL, 1021244, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4002a000
old_mmap(0x40120000, 12288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED, 3, 0xf6000) = 0x40120000
old_mmap(0x40123000, 1340, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40123000
close(3)                                = 0
open("/lib/libcrypto.so.4", O_RDONLY)   = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\260\250"...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=971612, ...}) = 0
old_mmap(NULL, 984792, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40124000
old_mmap(0x40200000, 69632, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED, 3, 0xdc000) = 0x40200000
old_mmap(0x40211000, 14040, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x40211000
close(3)                                = 0
open("/usr/lib/libisc.so.4", O_RDONLY)  = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0Pw\0\000"...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=216216, ...}) = 0
old_mmap(NULL, 215168, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x40215000
old_mmap(0x40249000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED, 3, 0x34000) = 0x40249000
close(3)                                = 0
open("/lib/libnsl.so.1", O_RDONLY)      = 3
read(3,
"\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0000<\0\000"...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=91368, ...}) = 0
old_mmap(NULL, 85184, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4024a000
old_mmap(0x4025c000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED, 3, 0x11000) = 0x4025c000
old_mmap(0x4025d000, 7360, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x4025d000
close(3)                                = 0
open("/lib/tls/libpthread.so.0", O_RDONLY) = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\300F\0"...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=97644, ...}) = 0
old_mmap(NULL, 64788, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4025f000
old_mmap(0x4026c000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED, 3, 0xc000) = 0x4026c000
old_mmap(0x4026d000, 7444, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x4026d000
close(3)                                = 0
open("/lib/tls/libc.so.6", O_RDONLY)    = 3
read(3,
"\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0000X\1\000"...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=1563240, ...}) = 0
old_mmap(NULL, 1272460, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x4026f000
old_mmap(0x403a0000, 12288, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED, 3, 0x130000) = 0x403a0000
old_mmap(0x403a3000, 10892, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x403a3000
close(3)                                = 0
open("/lib/libdl.so.2", O_RDONLY)       = 3
read(3,
"\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0P\32\0\000"...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=14728, ...}) = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0x403a6000
old_mmap(NULL, 12148, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x403a7000
old_mmap(0x403a9000, 4096, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED, 3, 0x1000) = 0x403a9000
close(3)                                = 0
open("/usr/lib/libz.so.1", O_RDONLY)    = 3
read(3, "\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0\340\31"...,
512) = 512
fstat64(3, {st_mode=S_IFREG|0755, st_size=52584, ...}) = 0
old_mmap(NULL, 55564, PROT_READ|PROT_EXEC, MAP_PRIVATE, 3, 0) = 0x403aa000
old_mmap(0x403b6000, 8192, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED, 3, 0xb000) = 0x403b6000
close(3)                                = 0
old_mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS,
-1, 0) = 0x403b8000
set_thread_area({entry_number:-1 -> -1, base_addr:0x403b8080,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0,
limit_in_pages:1, seg_not_present:0, useable:1}) = -1 ENOSYS (Function
not implemented)
modify_ldt(1, {entry_number:0, base_addr:0x403b8080, limit:1048575,
seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1,
seg_not_present:0, useable:1}, 16) = 0
munmap(0x40016000, 75053)               = 0
set_tid_address(0x403b80c8)             = -1 ENOSYS (Function not implemented)
rt_sigaction(SIGRTMIN, {0x40263620, [], SA_RESTORER|SA_SIGINFO,
0x40269df0}, NULL, 8) = 0
rt_sigprocmask(SIG_UNBLOCK, [RTMIN], NULL, 8) = 0
getrlimit(RLIMIT_STACK, {rlim_cur=8192*1024, rlim_max=RLIM_INFINITY}) = 0
rt_sigaction(SIGINT, {0x40233290, ~[RTMIN], SA_RESTORER, 0x40269df8},
NULL, 8) = 0
rt_sigaction(SIGTERM, {0x40233290, ~[RTMIN], SA_RESTORER, 0x40269df8},
NULL, 8) = 0
rt_sigaction(SIGPIPE, {SIG_IGN}, NULL, 8) = 0
rt_sigaction(SIGHUP, {SIG_DFL}, NULL, 8) = 0
rt_sigprocmask(SIG_BLOCK, [HUP INT TERM], NULL, 8) = 0
getpid()                                = 1561
socket(PF_INET, SOCK_STREAM, IPPROTO_IP) = 3
close(3)                                = 0
socket(PF_INET6, SOCK_STREAM, IPPROTO_IPrequ) = -1 EAFNOSUPPORT
(Address family not supported by protocol)
futex(0x402491f0, FUTEX_WAKE, 2147483647) = -1 ENOSYS (Function not implemented)
brk(0)                                  = 0x80566e8
brk(0x80776e8)                          = 0x80776e8
brk(0)                                  = 0x80776e8
brk(0x8078000)                          = 0x8078000
mmap2(NULL, 8392704, PROT_READ|PROT_WRITE|PROT_EXEC,
MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x403b9000
mprotect(0x403b9000, 4096, PROT_NONE)   = 0
clone(child_stack=0x40bb9b08,
flags=CLONE_VM|CLONE_FS|CLONE_FILES|CLONE_SIGHAND|CLONE_THREAD|CLONE_SYSVSEM|CLONE_SETTLS|CLONE_PARENT_SETTID|CLONE_CHILD_CLEARTID|CLONE_DETACHED,
parent_tidptr=0x40bb9bf8, {entry_number:0, base_addr:0x40bb9bb0,
limit:1048575, seg_32bit:1, contents:0, read_exec_only:0,
limit_in_pages:1, seg_not_present:0, useable:1},
child_tidptr=0x40bb9bf8) = 1562
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
+++ killed by SIGSEGV +++


Thanks in advance 
Shaz

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Vincent Hanquez

2005-Jul-30 11:24 UTC

head link

Re: [Xen-users] segmentation fault in xen nslookup

On Fri, Jul 29, 2005 at 10:37:35AM +0100, Shahzad Chohan
wrote:> Hi Guys,
> 
> I just managed to get rhel-3-ws working as a domU. The problem is that
> when I run the following nslookup command I get a segmentaion fault.
> Can anyone please shed a light on this. I''ve attached an strace,
if it
> helps.
> 
> open("/lib/tls/libc.so.6", O_RDONLY)    = 3
> read(3,
"\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0000X\1\000"...,
> 512) = 512
> fstat64(3, {st_mode=S_IFREG|0755, st_size=1563240, ...}) = 0
apparently you still have a tls libc enabled.
can you do a "chmod 000 /lib/tls" or "mv /lib/tls
/lib/tls.disabled" and
see if that fix it ?

-- 
Vincent Hanquez

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Ian Pratt

2005-Jul-30 13:18 UTC

head link

RE: [Xen-users] segmentation fault in xen nslookup

> > I just managed to get rhel-3-ws working as a domU. The 
> problem is that 
> > when I run the following nslookup command I get a segmentaion fault.
> > Can anyone please shed a light on this. I''ve attached an 
> strace, if it 
> > helps.
> > 
> > open("/lib/tls/libc.so.6", O_RDONLY)    = 3
> > read(3, 
> >
"\177ELF\1\1\1\0\0\0\0\0\0\0\0\0\3\0\3\0\1\0\0\0000X\1\000"...,
> > 512) = 512
> > fstat64(3, {st_mode=S_IFREG|0755, st_size=1563240, ...}) = 0
> 
> apparently you still have a tls libc enabled.
> can you do a "chmod 000 /lib/tls" or "mv /lib/tls 
> /lib/tls.disabled" and see if that fix it ?
I think there''s an RPM of a xen-firendly NPTL glibc for RHEL3 somewhere
on the wiki.

It''s slightly surprising that this was seg faulting, as we believe the
emulation is correct (though a bit slow). We should definitely check the
unstable.hg tree running on RHEL3 to see whether the issue is fixed.

Ian

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Vincent Hanquez

2005-Jul-30 16:05 UTC

head link

Re: [Xen-users] segmentation fault in xen nslookup

On Sat, Jul 30, 2005 at 02:18:49PM +0100, Ian Pratt
wrote:> > apparently you still have a tls libc enabled.
> > can you do a "chmod 000 /lib/tls" or "mv /lib/tls 
> > /lib/tls.disabled" and see if that fix it ?
> 
> I think there''s an RPM of a xen-firendly NPTL glibc for RHEL3
somewhere
> on the wiki.
> 
> It''s slightly surprising that this was seg faulting, as we believe
the
> emulation is correct (though a bit slow). We should definitely check the
> unstable.hg tree running on RHEL3 to see whether the issue is fixed.
some earlier message seems to indicate that he uses 2.4 though.
Redhat 2.4 kernels contains load of patches to support TLS and 2.4-xen0
kernels doesn''t have any support for that, hence the segfault.
I''ve seems the same scheme for openmosix.

for 2.6 it shouldn''t happen.

-- 
Vincent Hanquez

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Shahzad Chohan

2005-Aug-01 13:47 UTC

head link

Re: [Xen-users] segmentation fault in xen nslookup

On 7/30/05, Vincent Hanquez <vincent.hanquez@cl.cam.ac.uk>
wrote:> On Sat, Jul 30, 2005 at 02:18:49PM +0100, Ian Pratt wrote:
> > > apparently you still have a tls libc enabled.
> > > can you do a "chmod 000 /lib/tls" or "mv /lib/tls
> > > /lib/tls.disabled" and see if that fix it ?
> >
> > I think there''s an RPM of a xen-firendly NPTL glibc for RHEL3
somewhere
> > on the wiki.
> >
> > It''s slightly surprising that this was seg faulting, as we
believe the
> > emulation is correct (though a bit slow). We should definitely check
the
> > unstable.hg tree running on RHEL3 to see whether the issue is fixed.
> 
> some earlier message seems to indicate that he uses 2.4 though.
> Redhat 2.4 kernels contains load of patches to support TLS and 2.4-xen0
> kernels doesn''t have any support for that, hence the segfault.
> I''ve seems the same scheme for openmosix.
> 
> for 2.6 it shouldn''t happen.
> 
> --
> Vincent Hanquez
> 
Hey guys,

Many thanks for the replies. They proved to be really helpful. I''ve
moved the tls out of the way and things are working great now.

I''m using rhel 3 as the domU, with xen 2.0.6 as the xen version.

Thanks
Shaz

_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users

Xen users - Jul 2005 - segmentation fault in xen nslookup

[Xen-users] segmentation fault in xen nslookup

Re: [Xen-users] segmentation fault in xen nslookup

RE: [Xen-users] segmentation fault in xen nslookup

Re: [Xen-users] segmentation fault in xen nslookup

Re: [Xen-users] segmentation fault in xen nslookup