[lkml]   [2001]   [Apr]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: pthreads & fork & execve
    On Mon, Apr 02, 2001 at 09:54:25AM -0300, Gustavo Niemeyer wrote:
    > 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.

    By any chance, are you dlopening a DSO linked against -lpthread from
    program not linked against -lpthread?

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 13:22    [W:0.020 / U:11.092 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site