Zsh Mailing List Archive
Messages sorted by:
Re: Help needed with execcmd() (was: Re: Cant fg a suspended su (4.1.0-dev-7))
- X-seq: zsh-workers 18317
- From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: Help needed with execcmd() (was: Re: Cant fg a suspended su (4.1.0-dev-7))
- Date: Sat, 1 Mar 2003 18:42:10 +0000
- In-reply-to: <87smuaw1o9.fsf_-_@xxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <200302211807.h1LI74n23531@xxxxxxxxxxxxxxxxxxxxxxxxx> <1030222230416.ZM10265@xxxxxxxxxxxxxxxxxxxxxxx> <87n0kl19el.fsf@xxxxxxxxxxxxxxxx> <87smuaw1o9.fsf_-_@xxxxxxxxxxxxxxxx>
On Feb 27, 12:47am, Philippe Troin wrote:
} Subject: Help needed with execcmd() (was: Re: Cant fg a suspended su (4.1.
} Could somebody familiar with Src/exec.c point out for me where I can
} insert a statement where the following conditions are true:
I'm not sure I can tell you that, but ...
} - I can find out if we are doing a real exec(), not a "fake" exec
} (BTW, what's a "fake" exec?)
A "fake" exec means that the current shell has state that must explicitly
be cleaned up after the external command begins, so the shell can't just
replace its process image with that of the new process. Instead it forks,
but then [eventually] exits to simulate an exec having taken place.
As noted in one of the comments in exec.c, this is similar to the case
where the command to be exec'd is a builtin.
} following a "exec blah" command
} line. For example, in execcmd(), I can find this out with the
} do_exec variable.
The shell will never do a real exec on do_exec false, but do_exec true
does not imply the opposite. A fake exec could still occur. If you're
in the code beyond the comment that reads
/* Make a copy of stderr for xtrace output before redirecting */
then (is_exec == 1 && forked == 0) means it's a real exec; before the
big comment about "Do we need to fork?" the test is more complex.
} - the terminal (SHTTY) is still open
This should be true any time SHTTY > -1.
} - there will be no more terminal or process group ids changes before
} we hit zexecve() (meaning no more attachtty(), nor setpgrp())
} I can't seem to find a spot where all three conditions are true.
I'm not 100% certain, but I don't think there is a spot where all three
conditions are true, because of the side-effects of the STTY environment
variable. There may be a spot where all three plus "STTY is not set"
are true, but it'd have to be after all the redirections have been
processed, so probably it's never true until somewhere inside the
Messages sorted by: