os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Move the truss item from "Must for 5.0RC1" to "Desired for 5.0", as the

Browse source 
problems may be somewhat deeply ingrained.  I'd still like to see a
fix in place for 5.0, but we can't hold up 5.0RC1 for it today.
This commit is contained in:
Robert Watson 2002-12-03 19:33:13 +00:00
parent 98467791b6
commit 8004bd5124
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=15143
1 changed files with 13 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

27
en/releases/5.0R/todo.sgml
View file

@ -1,7 +1,7 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD: www/en/releases/5.0R/todo.sgml,v 1.68 2002/12/03 14:22:58 rwatson Exp $">
<!ENTITY date "$FreeBSD: www/en/releases/5.0R/todo.sgml,v 1.69 2002/12/03 15:41:42 rwatson Exp $">
<!ENTITY title "FreeBSD 5.0 Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
@ -32,19 +32,6 @@
reviewed and fixed.</td>
</tr>
<tr>
<td>Race conditions in truss</td>
<td>Debugging and fixing in progress</td>
<td>robert@</td>
<td>Truss appears to contain a race condition during the start-up of
debugging, which can result in truss failing to attach to the process
before it exits. The symptom is that truss reports that it cannot
open the procfs node supporting the process being debugged. A bug
also appears to exist where in truss will hang if execve() returns
ENOENT. A further race appears to exist in which truss will return
"PIOCWAIT: Input/output error" occasionally on startup.</td>
</tr>
<tr>
<td>Many reported problems with disklabel -e</td>
<td>--</td>
@ -339,6 +326,18 @@
the SMPng draft architecture should be updated and committed.</td>
</tr>
<tr>
<td>Race conditions in truss</td>
<td>Debugging and fixing in progress</td>
<td>robert@</td>
<td>Truss appears to contain a race condition during the start-up of
debugging, which can result in truss failing to attach to the process
before it exits. The symptom is that truss reports that it cannot
open the procfs node supporting the process being debugged. A bug
also appears to exist where in truss will hang if execve() returns
ENOENT. A further race appears to exist in which truss will return
"PIOCWAIT: Input/output error" occasionally on startup.</td>
</tr>
</table>
<h3>Areas requiring immediate testing due to 5.0 changes</h3>