Re: pthreads & fork & execve
> People making Apache 1.3.X modules have a problem too. They have to > rebuilt Apache and add -lpthread if any modules uses threads. It seems to be the same case here. > The following small program illustrates this. The program, main-wot, > crashes - the other, main-wt, doesn't. [...] Both work here... am I doing something wrong (or right :-)?? I've tried to reduce to a testcase like this before, and it has worked as well. I don't understand what this limitation is about. -- Gustavo Niemeyer [ 2AAC 7928 0FBF 0299 5EB5 60E2 2253 B29A 6664 3A0C ] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: pthreads & fork & execve
Hello Jakub!! [...] > By any chance, are you dlopening a DSO linked against -lpthread from > program not linked against -lpthread? Yes, I am!! Is this some limitation I'm not aware of? Indeed, this seems to be made in many cases... is this about pthread?? -- Gustavo Niemeyer [ 2AAC 7928 0FBF 0299 5EB5 60E2 2253 B29A 6664 3A0C ] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: pthreads & fork & execve
Hi Richard! Hi Dennis! > I tracked this down to a corrupt jumptable somewhere in the pthreads > part of the libc (didnt have the source handy at that time, though). So > I think this is a libc bug (version does not matter) - I even did a > followup to a similar bug in the libc gnats database (I think I should > have opened a new one, though...). But I failed to construct a "simple" > testcase showing the bug (We use rather large amount of threads and > in one or two doing popen() calls - or handcrafted fork() && execv(), > the SIGSEGV is during fork()). We're going trough two similar problems here. One is KDE, and the other is Linuxconf. Linuxconf is core dumping on a module when it is linked with pthread and dlopen()'ed with RTLD_GLOBAL. We must reduce one of them to a testcase. Btw, both are mainly C++ programs. Is your software written in C++? > I stopped trying to find out what is going on as this feature is not > essential (but maybe useful in the future). So I suggest you build a > libc from source with debugging on and trace it down to the actual > libc problem - or better try to isolate a simple testcase. We'll probably do this here... > I like to hear from the results :) Please, let me know as well! :-) Thanks!! -- Gustavo Niemeyer [ 2AAC 7928 0FBF 0299 5EB5 60E2 2253 B29A 6664 3A0C ] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: can not compile 2.4.3 on alpha
Hello Andrejs!! > [linux] make dep;make clean;make boot [...] > /usr/src/linux-2.4.3/include/asm/pgalloc.h:334: conflicting types for > `pte_alloc' > /usr/src/linux-2.4.3/include/linux/mm.h:399: previous declaration of > `pte_alloc' > /usr/src/linux-2.4.3/include/asm/pgalloc.h:352: conflicting types for > `pmd_alloc' > /usr/src/linux-2.4.3/include/linux/mm.h:412: previous declaration of > `pmd_alloc' > make: *** [init/main.o] Error 1 [...] This is happening on ia64 as well. The interface seems to have changed but some architectures were forgotten. -- Gustavo Niemeyer [ 2AAC 7928 0FBF 0299 5EB5 60E2 2253 B29A 6664 3A0C ] - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
