dave@micropen (David F. Carlson) (05/12/88)
Sdb(1) introduces an unnecessary difference to programs forked under it
and the programs that are in turn forked. The problem is partially
related to CLOSE_ON_EXEC option of fcntl(2) not working under SV/386.
(Close on exed bug has been reported to Microport since Jan 88. The
bug goes all the way back to Interactive port, I suspect.)
Programs run under sdb(1) have the capability of having opened *source*
files that sdb has opened when it fork/execs the traced process. Files
are also needlessly open in all subsequent children, etc.
Fixes are obviously to fix the close on exec functionality or to close
all source files within sdb for the r(un) command.
--
David F. Carlson, Micropen, Inc.
...!{ames|harvard|rutgers|topaz|...}!rochester!ur-valhalla!micropen!dave
"The faster I go, the behinder I get." --Lewis Carroll