#162 Crashes in libpthread after migration

Migration (51)

During our evaluation tests of openmosix, we
encountered several crashes of applications that are
linked against libpthread, although they were not using
any threads. Crashes always occurred after the process

To reproduce, compile the attached program, link it
with -lpthread, run it, and follow the instructions on
the screen.
For me it crashes 99% of the time.

#0 0x40030476 in pthread_mutex_unlock () from
#1 0x40032ad4 in funlockfile () from
#2 0x400db9ed in fgets () from /lib/i686/libc.so.6
#3 0x08048600 in main ()

For other crash scenarios, refer to the
openmosix-general mailing list ("segfault in
libpthread", 7/5/2005,

Relevant system information:

Red Hat Enterprise Linux AS release 3 (Taroon Update 4)

Kernel: vanilla 2.4.26
OM: 2.4.26
Glibc: glibc-2.3.2-95.30
Gcc: gcc-3.2.3-47

The tests were run on a cluster of 3 dual-processor AMD
servers, where I was the sole user and the load was
nearly 0 all the time.

BTW: the problems disappear when I set LD_ASSUME_KERNEL
to 2.2.18, or when /lib/i686 is made inaccessible.

I hope this information is helpful in solving this bug.


  • Eddy De Greef

    Eddy De Greef - 2005-07-11

    Program to reproduce a pthread migration crash

  • Moshe Bar

    Moshe Bar - 2005-09-26
    • milestone: 460484 --> v2.6.9(openMosix 2.0.0)
    • priority: 5 --> 6
    • status: open --> pending
  • SourceForge Robot

    • status: pending --> closed
  • SourceForge Robot

    Logged In: YES

    This Tracker item was closed automatically by the system. It was
    previously set to a Pending status, and the original submitter
    did not respond within 30 days (the time period specified by
    the administrator of this Tracker).

  • Eddy De Greef

    Eddy De Greef - 2005-10-27

    Logged In: YES

    What was I supposed to respond to? Nobody asked anything.


Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

JavaScript is required for this form.

No, thanks