Project

General

Profile

Bug #1135

Handle locked by flockfile() remain locked in child process (after fork())

Added by Dmitry Moskalchuk almost 4 years ago. Updated almost 4 years ago.

Status:
Open
Priority:
Normal
Category:
libcrystax
Target version:
Start date:
11/11/2015
Due date:
% Done:

0%

Estimated time:
CPU Architecture:
Host OS:
Toolchain:
Android version:
CrystaX Version:

History

#1

Updated by Dmitry Moskalchuk almost 4 years ago

  • Status changed from Open to In Progress
#2

Updated by Dmitry Moskalchuk almost 4 years ago

  • Subject changed from fork() test timeout to Handle locked by flockfile() remain locked after fork() in child process
  • Description updated (diff)
  • Status changed from In Progress to Open
  • Target version changed from 10.3.0 to 11.0.0

On GNU/Linux with glibc, it become unlocked in child process after fork(), no matter what was its state in parent process. However, in BSD it inherit state from parent. It's unclear now which behaviour is proper for Android, so lowering priority

#3

Updated by Dmitry Moskalchuk almost 4 years ago

  • Blocked by Task #1146: Implement pthread_atfork() added
#4

Updated by Dmitry Moskalchuk almost 4 years ago

  • Blocked by deleted (Task #1146: Implement pthread_atfork())
#5

Updated by Dmitry Moskalchuk almost 4 years ago

  • Priority changed from High to Normal
#6

Updated by Dmitry Moskalchuk almost 4 years ago

  • Subject changed from Handle locked by flockfile() remain locked after fork() in child process to Handle locked by flockfile() remain locked in child process (after fork())

Also available in: Atom PDF