|
Message-ID: <20140321190954.GM26358@brightrain.aerifal.cx> Date: Fri, 21 Mar 2014 15:09:54 -0400 From: Rich Felker <dalias@...ifal.cx> To: musl@...ts.openwall.com Subject: Re: Build on linux 2.6 and run on linux 2.4? On Fri, Mar 21, 2014 at 02:24:09PM -0400, John Mudd wrote: > $ cat /etc/*-release > LSB_VERSION="1.3" > Red Hat Enterprise Linux AS release 3 (Taroon) It looks to me like this comes from around the time RH was developing NPTL, and they may have already added the necessary kernel-side stuff into their 2.4 kernel. Try running: getconf GNU_LIBPTHREAD_VERSION and see if it reports NPTL or LinuxThreads. > logfile: > 25920 execve("/home/jmudd/test_threads2", ["test_threads2"], [/* 26 vars > */]) = 0 > 25920 rt_sigprocmask(SIG_UNBLOCK, [RT_1 RT_2], NULL, 8) = 0 > 25920 set_thread_area({entry_number:-1 -> 6, base_addr:0x804e540, > limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, > seg_not_present:0, useable:1}) = 0 > 25920 set_tid_address(0x804e558) = 25920 > 25920 mmap2(NULL, 90112, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = > 0xb75ea000 > 25920 mprotect(0xb75eb000, 86016, PROT_READ|PROT_WRITE) = 0 > 25920 clone(child_stack=0xb75fff30, > 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=0xb75fff58, {entry_number:6, base_addr:0xb75fff40, > limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, > seg_not_present:0, useable:1}, child_tidptr=0xb75fff58) = 25921 > 25920 mmap2(NULL, 90112, PROT_NONE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = > 0xb75d4000 > 25920 mprotect(0xb75d5000, 86016, PROT_READ|PROT_WRITE) = 0 > 25920 clone(child_stack=0xb75e9f30, > 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=0xb75e9f58, {entry_number:6, base_addr:0xb75e9f40, > limit:1048575, seg_32bit:1, contents:0, read_exec_only:0, limit_in_pages:1, > seg_not_present:0, useable:1}, child_tidptr=0xb75e9f58) = 25922 > 25920 futex(0xb75fff58, FUTEX_WAIT, 25921, NULL <unfinished ...> > 25922 --- SIGSTOP (Stopped (signal)) @ 0 (0) --- > 25922 --- SIGSTOP (Stopped (signal)) @ 0 (0) --- > 25920 <... futex resumed> ) = -1 EINTR (Interrupted system call) > 25922 --- SIGSTOP (Stopped (signal)) @ 0 (0) --- > 25920 --- SIGSTOP (Stopped (signal)) @ 0 (0) --- > 25920 futex(0xb75fff58, FUTEX_WAIT, 25921, NULL <unfinished ...> > 25921 --- SIGSTOP (Stopped (signal)) @ 0 (0) --- > 25921 --- SIGSTOP (Stopped (signal)) @ 0 (0) --- > 25920 <... futex resumed> ) = -1 EINTR (Interrupted system call) > 25921 --- SIGSTOP (Stopped (signal)) @ 0 (0) --- > 25920 --- SIGSTOP (Stopped (signal)) @ 0 (0) --- These SIGSTOPs are weird, but otherwise I don't see anything strange. In particular set_thread_area and set_tid_address worked; AFAIK they should have failed on a "real" 2.4 kernel. Rich
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.