blissnd / golang_multi_thread_system_call

GoLang system call issue with workaround

Workaround for issue with system call from multiple threads in parallel

Demo of issue.

go build test_concurrency.go

./test_concurrency.go

Running the functions sequentially:

Current directory from change_into_directory_1(): *** This is file 1 ***

Current directory from change_into_directory_2(): *** This is file 2 ***

--------------- Running the functions in parallel ---------------

Current directory from change_into_directory_2(): Current directory from change_into_directory_1(): *** This is file 2 ***

<<< ERROR getting file 1 from directory 1>>>

---

O/S system calls to change the directory in thread_1 & thread_2 [functions change_into_directory_1() & change_into_directory_2()] are not remaining indenpendent of one another. They seem to be sharing system state resources underneath, implying the code is not re-entrant.

EXPECTED BEHAVIOUR: That thread_2 does not reflect the current O/S directory state of thread_1 and operates independently of thread_1 including at the O/S level, so that the functions which are run in parallel remain fully re-entrant from the point-of-view of the caller.

JAVA CASE

Java copes with a similar use case. To run the java:

cd JAVA_TEST

javac *.java

java Concurrency_Test