Update of bug #48919 (project hurd):
Status: None => Fixed
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #1:
Mmm, indeed. Normally, exec_setexecdata is called at boot, because
startup calls proc_setexecdata, which in turn calls exec_setexecdata.
Let's just make the code stronger for now, it makes sense anyway. We
however may need to initialize std_ports automatically to make using a
sub exec easier. We "just" need to determine what makes sense.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?48919>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
