Date: Tue, 23 Mar 2004 17:37:51 -0800 (PST) From: Marcel Moolenaar <marcel@FreeBSD.org> To: Perforce Change Reviews <perforce@freebsd.org> Subject: PERFORCE change 49603 for review Message-ID: <200403240137.i2O1bpIE091578@repoman.freebsd.org>
next in thread | raw e-mail | index | archive | help
http://perforce.freebsd.org/chv.cgi?CH=49603 Change 49603 by marcel@marcel_nfs on 2004/03/23 17:36:54 I'm not going to bust my balls over this. Just assign the thread the same ID as the process for a fork(). This way most threads get an unique ID. The only threads that won't have an ID this way are those created for 1:1 or M:N threading support. I don't care about that while working on the fundamental threading support. Affected files ... .. //depot/projects/gdb/sys/kern/kern_fork.c#7 edit Differences ... ==== //depot/projects/gdb/sys/kern/kern_fork.c#7 (text+ko) ==== @@ -498,6 +498,7 @@ #undef RANGEOF td2->td_sigstk = td->td_sigstk; + td2->td_tid = p2->p_pid; /* Set up the thread as an active thread (as if runnable). */ ke2->ke_state = KES_THREAD;
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200403240137.i2O1bpIE091578>