[Mono-bugs] [Bug 68141][Maj] Changed - forking problems
bugzilla-daemon@bugzilla.ximian.com
bugzilla-daemon@bugzilla.ximian.com
Wed, 13 Oct 2004 09:11:55 -0400 (EDT)
Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.
Changed by dick@ximian.com.
http://bugzilla.ximian.com/show_bug.cgi?id=68141
--- shadow/68141 2004-10-12 21:08:25.000000000 -0400
+++ shadow/68141.tmp.3310 2004-10-13 09:11:55.000000000 -0400
@@ -1,13 +1,13 @@
Bug#: 68141
Product: Mono: Runtime
Version: unspecified
OS: unknown
OS Details:
-Status: NEW
-Resolution:
+Status: RESOLVED
+Resolution: NOTABUG
Severity: Unknown
Priority: Major
Component: misc
AssignedTo: mono-bugs@ximian.com
ReportedBy: james@ximian.com
QAContact: mono-bugs@ximian.com
@@ -28,6 +28,19 @@
------- Additional Comments From james@ximian.com 2004-10-12 21:08 -------
For me, when running the test, it dies after "Configuring..." gets
printed (it never prints "Configured." or sleeps).
This remoting config stuff is just one of the things that I've found
that causes this. I'm not sure how it's significant other than that.
+
+------- Additional Comments From dick@ximian.com 2004-10-13 09:11 -------
+Quoting from Butenhof's "Programming with POSIX Threads", p197, s6.1:
+
+"When a threaded process calls fork to create a child process,
+Pthreads specifies that only the thread calling fork exists in the
+child. ... Pthreads does not 'terminate' the other threads in a forked
+process...They simply cease to exist. ... This is not a problem if
+the child process is about to call exec to run a new program, but if
+you use fork to clone a threaded program, beware that you may lose
+access to memory, especially heap memory stored only as
+thread-specific data values."
+